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
..
__init__.py
addsub.py insn: use records to define instruction encodings. 2 years ago
bcd.py insn: use records to define instruction encodings. 2 years ago
branch.py insn: use records to define instruction encodings. 2 years ago
byterev.py insn: use records to define instruction encodings. 2 years ago
compare.py insn: use records to define instruction encodings. 2 years ago
cr.py insn: use records to define instruction encodings. 2 years ago
loadstore.py insn: use records to define instruction encodings. 2 years ago
logical.py insn: use records to define instruction encodings. 2 years ago
msr.py insn: use records to define instruction encodings. 2 years ago
muldiv.py insn: use records to define instruction encodings. 2 years ago
rotate.py insn: use records to define instruction encodings. 2 years ago
spr.py insn: use records to define instruction encodings. 2 years ago
syscall.py insn: use records to define instruction encodings. 2 years ago
trap.py insn: use records to define instruction encodings. 2 years ago
utils.py