-
Notifications
You must be signed in to change notification settings - Fork 90
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
xperm.b / xperm.n /rev.b mnemonics #115
Comments
These are bitmanip instructions, albeit didn't make it into the document in public review. Change of instruction names should perhaps be debated in the bitmanip mailing list as well. |
- renamed revb -> brev8 - renamed xpermn -> xperm4 - renamed xpermb -> xperm8 On branch dev/ben/zbk Your branch is up-to-date with 'ben-marshall/dev/ben/zbk'. Changes to be committed: renamed: revb.adoc -> brev8.adoc renamed: xpermn.adoc -> xperm4.adoc renamed: xpermb.adoc -> xperm8.adoc
- renamed revb -> brev8 - renamed xpermn -> xperm4 - renamed xpermb -> xperm8 On branch dev/ben/zbk Your branch is up-to-date with 'ben-marshall/dev/ben/zbk'. Changes to be committed: renamed: revb.adoc -> brev8.adoc renamed: xpermn.adoc -> xperm4.adoc renamed: xpermb.adoc -> xperm8.adoc
@kasanovic @mjosaarinen @ben-marshall
If you are into removing dots, you may want to name this instruction |
It is difficult to be completely consistent in mnemonic convention, but these are parallel packed-SIMD-style instructions. In the P extension, the assembler mnemonic convention has element size (e.g., 8 or 16) in mnemonic. Also, in vector extension number of bits per element appears in some instructions (e.g., le8.v). rev8 also has that pattern.
The .b appears in sext.b as single-byte operand (not packed).
Zbb orc.b is an unfortunate outlier as it probably should have been orc8.
xperm8 and xperm4 seem more consistent to me.
rev.b is also awkward. e.g., brev8 is more consistent to me
The text was updated successfully, but these errors were encountered: