[Libre-soc-isa] [Bug 213] SimpleV Standard writeup needed

[bugzilla-daemon at libre-soc.org]

https://bugs.libre-soc.org/show_bug.cgi?id=213

--- Comment #12 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to Cole Poirier from comment #11)
> (In reply to Luke Kenneth Casson Leighton from comment #10)
> > (In reply to Cole Poirier from comment #9)
> 
> > they have a selection method based on the column name (see PowerDecoder2
> > or more specifically DecodeInA spr_out field) however we are not
> > going to do parallel/vector SPR read/writes/operations.
> 
> Interesting!
>  
> > > but it seems that all rows are 'unique',
> > 
> > that's why i said strip the opcode, strip the comment column, strip the
> > function unit column (and the sgl column).  as in: destroy / remove entirely.
> 
> I remember, I did that, there were no duplicates...
> 
> > oh, and now that i look at it: strip (destroy, remove) the opcode column as
> > well
> > 
> > opcode,unit,internal op,in1,in2,in3,out,CR in,CR out,inv A,inv out,cry
> > in,cry out,ldst len,BR,sgn ext,upd,rsrv,32b,sgn,rc,lk,sgl pipe,comment,form
> > 
> > -->
> > 
> > in1,in2,in3,out,CR in,CR out,inv A,inv out,cry in,cry out,ldst len,BR,sgn
> > ext,upd,rsrv,32b,sgn,rc,lk,form
> > 
> > we probably also don't want the "form" field, or the "inv A" or "inv out"
> > or "rsrv" because those are cache-related not register-related.
> > 
> > -->
> > 
> > in1,in2,in3,out,CR in,CR out,cry in,cry out,ldst len,BR,sgn
> > ext,upd,32b,sgn,rc,lk
> > 
> > there's just no way that after stripping all those columns there are no
> > duplicates.
> 
> This did work in constrast to the the more inclusive above set of columns.
> Reduced from 259 rows to 131. 
>  
> > can you drop the results into the wiki, so we can take a look.
> 
> Done here: https://libre-soc.org/openpower/opcode_regs_deduped

whatever software you used is not very good, cat | sort | uniq removed about 5
more!

it also converted numbers to floating point which we don't really want either.

> Although I haven't done the join with the original opcode column. Do you
> want just that final product or both?

given that we will need to add FP and otger opcodes, a manual process is
probably not a good idea.  however it is a start and we need to know what we
are looking at.

oh, now i have seen it: can you also "process" the LDSTLEN field so that it is
either "1" or "0"?  this will cut another... 10-20 estimated rows.

-- 
You are receiving this mail because:
You are on the CC list for the bug.