You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Jean-François Nguyen 331e4b76ba insn: use records to define instruction encodings. ... Before this commit, instructions were defined by a sequence of Const for fixed fields (e.g. PO/XO) and AnyConst for others (e.g. operands). This approach restricted their use to BMC use-cases, and prevented them from appearing in VCD traces. After this commit, an instruction encoding is defined by a Record. As fields can now be set to arbitrary values, the corresponding InsnSpec will only assert `pfv.stb` if `pfv.insn` matches a valid encoding (i.e. fixed fields have correct values). On the other side, BMC testbenches will drive `pfv.insn` with an AnyConst, and assume `pfv.stb` is high.		2 years ago
..
insn	insn: use records to define instruction encodings.	2 years ago
__init__.py	session: save results and counter-examples to a local directory.	2 years ago
_timer.py	In-depth refactoring, improved user interface.	2 years ago
all.py	Add liveness check.	2 years ago
causal.py	Add causal consistency check.	2 years ago
cia.py	In-depth refactoring, improved user interface.	2 years ago
gpr.py	pfv.Interface: add support for skipping instructions.	2 years ago
liveness.py	Add liveness check.	2 years ago
storage.py	Add instruction storage check.	2 years ago
unique.py	In-depth refactoring, improved user interface.	2 years ago