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
It has some interesting implications for eve. In particular the vector length is not encoded in the register name or instruction, it's set elsewhere and can vary. I believe that the specific hardware implementation sets a maximum (up to 65kbits at this time) and I also believe that the user can dynamically set their desired length dynamically with vsetvli.
In any case, this should be fun and may become important as more of the industry adopts RISC-V.
featureNew feature or requestR&DThis mandates discussions before being applied
1 participant
Converted from issue
This discussion was converted from issue #1412 on February 09, 2023 18:15.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The RISC-V "V" Standard Vector Instructions specification has reached version 1.
https://github.com/riscv/riscv-v-spec
https://github.com/riscv/riscv-v-spec/releases
It has some interesting implications for eve. In particular the vector length is not encoded in the register name or instruction, it's set elsewhere and can vary. I believe that the specific hardware implementation sets a maximum (up to 65kbits at this time) and I also believe that the user can dynamically set their desired length dynamically with
vsetvli
.In any case, this should be fun and may become important as more of the industry adopts RISC-V.
Beta Was this translation helpful? Give feedback.
All reactions