Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Legal combinations table does not require zmmul / m-ext. #129

Open
marcfedorow opened this issue Jan 18, 2022 · 0 comments
Open

Legal combinations table does not require zmmul / m-ext. #129

marcfedorow opened this issue Jan 18, 2022 · 0 comments

Comments

@marcfedorow
Copy link

So formally rv32i_zbpbo_zpn is a legal combination and no zmmul insns (incl. MULH) are enabled.
This should be somehow solved (i.e. add M or zmmul as a required extention to this table).

Also spec should clearly define a string that rv32ip expands to.
I.e. it could expand to

  • rv32i_zmmul_zbpbo_zpn;
  • rv32i_zmmul_zbpbo_zpn_zpsfoperand;
  • rv32im_zbpbo_zpn;
  • rv32im_zbpbo_zpn_zpsfoperand.

While this four isa strings are all legal, rv32ip may expand only to one of them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant