| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
instruction-to-instructionstate
|
|
|
|
|
|
symbol/memory address list.
|
|
|
|
|
|
registers we might read that we want values for (particularly the PC)
|
|
Add a function from instruction to istate
|
|
|
|
|
|
|
|
Bytevectors; add place holder for memory size dependency tracking
|
|
|
|
this is quite specific to Power's spec)
|
|
|
|
instead of internal actions
|
|
then hits an error. So still in progress
Note: moved barrier kind changes to interp_interface, along with other memory kinds
|
|
|
|
Also adding more comments and getting the ml files built in the build process
|
|
Now when mode.track_values is true, on every register read, the returned value is tainted with the register it came from. This tracking is followed through every operation the interperter touches (except library functions, to be completed next).
One a memory operation involving a tracked value, there is optionally list of registers that value arose from in the memory request (i.e. maybe (list reg_name)).
|
|
remember why) for ppcmem integration.
|
|
|
|
|
|
|
|
|