cores
/
power-fv
3
1
Fork 0
Code Issues 18 Pull Requests Projects Releases Wiki Activity
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.
dinofly
main
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '331e4b76ba'
${ noResults }
power-fv/power_fv/insn
History
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
..
spec insn: use records to define instruction encodings. 2 years ago
__init__.py insn: use records to define instruction encodings. 2 years ago
const.py Add checks for multiplication/division instructions. 2 years ago
field.py Add checks for CR Move / Set Boolean instructions. 2 years ago