summaryrefslogtreecommitdiff
path: root/src/lem_interp
AgeCommit message (Collapse)Author
2014-08-27Changes to get another (slightly larger) executable running;Kathy Gray
adding executable as a test as well
2014-08-26small changes for armKathy Gray
2014-08-21Improve printing of function calls in stepper modeKathy Gray
2014-08-21Allow command line interface to exhaustively evaluate the next step, ↵Kathy Gray
printing the events. Note: this commit switches back to a standard lem build located in ~/bitbucket/lem/lem
2014-08-20Add ability to track register dependencies in interactive stepper; thus ↵Kathy Gray
testing register tracking/tainting
2014-08-19make test_power_interactive working again; now using interp_interface ↵Kathy Gray
instead of internal actions
2014-08-19Add file that actually drives command line interpreterKathy Gray
2014-08-18Handling many register reads, writes, and memory reads.Kathy Gray
There are problems that warrant discussion about handling special registers that hold records or data structures previously.
2014-08-18fix compile errorKathy Gray
2014-08-18Switch run_power to use interp_interface. Compilers and begins running, and ↵Kathy Gray
then hits an error. So still in progress Note: moved barrier kind changes to interp_interface, along with other memory kinds
2014-08-18wib?Peter Sewell
2014-08-18make interp_exhaustive not take an interp_mode argumentPeter Sewell
2014-08-18tweak barrier kinds in interface (likely needs changes elsewhere)Peter Sewell
2014-08-14Small tweaks to interp_interface interfaceKathy Gray
Also adding more comments and getting the ml files built in the build process
2014-08-13Update library functionsKathy Gray
2014-08-13FInd/fix a redundant case now that warnings are manageableKathy Gray
2014-08-13Complete tainting phase 1Kathy Gray
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)).
2014-08-12taint tracking through most of interpreterKathy Gray
Need to add cases for tracking a taint past a conditional check where possible; and then to actually generate them from reading registers.
2014-08-12more taint tracking, yet againKathy Gray
2014-08-11More taint tracking.Kathy Gray
Catch interp_inter_imp up with interp. WARNING: This commit triggers an exponential performance bug in Lem. To alleviate this bug, I am running with a locally modified Lem that has line 1321 of lem/src/typed_ast.ml commented out (On my laptop, I gave up trying to compile after about 900 seconds; beefier computers May be able to run unmodified, I don't know)
2014-08-09More tracking register dependency; another check point that compiles in ↵Kathy Gray
under two minutes
2014-08-08Tracking register dependence.Kathy Gray
Check point where Lem will compile interpreter in under 2 minutes
2014-08-07Fix bug introduced by last commitKathy Gray
2014-08-07Track taints across machine calls.Kathy Gray
This introduced a bug in vector.sail, commented out and needs to be fixed.
2014-08-05start tainting values with register dependenciesKathy Gray
2014-08-01Support separated memory read/write functions.Kathy Gray
Also allows register writing functions to be on the left hand side of an assignment in the same way. The last parameter to a writing function is the value to be written, and should appear on the right hand side of an assignment expression.
2014-07-30working dec vectorsKathy Gray
2014-07-25Add another type signature needed (we think but Susmit and I can't quite ↵Kathy Gray
remember why) for ppcmem integration.
2014-07-25Additional functions for interfaceKathy Gray
2014-07-18Writing to concatenated aliasesKathy Gray
2014-07-16Reading from an alias to two concatenated registers; not writing yet.Kathy Gray
2014-07-16Get writing working for aliases in the interpreter, other than concatenation.Kathy Gray
2014-07-15Finishing up some of the support for ExitKathy Gray
2014-07-14Add register to alias concatenation typeKathy Gray
2014-07-14Initial support for aliases and exit through the type system and the ↵Kathy Gray
interpreter. An alias can be read within the interpreter, but not written to. Exits aren't yet taken in the interpreter.
2014-07-03Adjust behavior on Unknown values in pattern match to stop matching as soon ↵Kathy Gray
as a pattern is matched without using an unknown; also causes full expansion on function calls with unknowns matched in patterns, however the local state is not reset.
2014-07-02Fix ordering issue in vector-concat pattern matchingGabriel Kerneis
2014-07-01Update case of EXTSGabriel Kerneis
2014-06-30Support for nondeterministic blocksKathy Gray
2014-06-25Add support for memory barrierKathy Gray
2014-06-25Add support for actions that read just a slice or single bit of a registerKathy Gray
2014-06-24Get enumerations working in interpreterKathy Gray
(plus a few other small related corrections)
2014-06-24Get vector length for to_inc_vec and to_dec_vec from the type system after ↵Kathy Gray
constraint solving (instead of hardcoding 64 as the default).
2014-06-23Get indexed vectors, particularly with default values, workingKathy Gray
2014-06-19Add mod:vec->range->vecGabriel Kerneis
2014-06-18Fix mod_vec in libraryGabriel Kerneis
2014-06-18Add definition of mod to libKathy Gray
2014-06-18Make hex constants work; improve utility of casts for selecting overloaded ↵Kathy Gray
functions
2014-06-12Interpret when an unknown is inserted into the program by interp_exhaustiveKathy Gray
Short version of below; ready to hook interp_exhaustive up to something to test, but haven't yet. If an unknown value influences a pattern match within an expression, each passing pattern is found and the bodies strung together into a block with let expressions to bind the variables. In a function call, the cases are all collected but the support is not in place at the moment to evaluate them. If an unknown is the result of the cond expression in an if, the then and else case become a block. Unknowns within the interpreter propagate to more Unknowns; also for some but not all library functions yet.
2014-06-11Equality between range and bit vectorGabriel Kerneis
The type-constraints are inspired from those for (+). They seem to work but I am not sure they make sense. The vector is interpreted as unsigned.