You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The nf field is treated as a variable arg within the rv_v instruction encoding file.
As I am interested in having all rvv instructions present in the YAML output, I was wondering whether a PR that expands this would get accepted? I believe this would align better with other extensions present in the dict e.g. Zimop and Zcmop.
I can see 3 possible solutions:
Expand rv_v file to include all of the instructions
Expand rv_v file to include all of the instructions, with the new instructions encoded as $pseudo_op (following what is done in rv_zimop and rv_zcmop)
Edit parse.py to expand dictionary only for the YAML output - avoid altering other outputs.
The text was updated successfully, but these errors were encountered:
Whatever we end up doing here, for backwards compatibility we need to make sure that the existing definitions that end up in encoding.out.h, inst.chisel, etc. are retained.
Whatever we end up doing here, for backwards compatibility we need to make sure that the existing definitions that end up in encoding.out.h, inst.chisel, etc. are retained.
Hi @aswaterman,
Could you please take a look at the proposed solution in this PR?
The nf field is treated as a variable arg within the rv_v instruction encoding file.
As I am interested in having all rvv instructions present in the YAML output, I was wondering whether a PR that expands this would get accepted? I believe this would align better with other extensions present in the dict e.g. Zimop and Zcmop.
I can see 3 possible solutions:
The text was updated successfully, but these errors were encountered: