2 ms·
They really should update the github to reflect that this has been ratified for years. (since Nov 2021, see: https://wiki.riscv.org/display/HOME/Recently+Ratifi
by camel-cdr 3y ago
They really should update the github to reflect that this has been ratified for years. (since Nov 2021, see: https://wiki.riscv.org/display/HOME/Recently+Ratified+Extensions https://wiki.riscv.org/display/HOME/Recently+Ratified+Extens...)
- brucehoult 3y agohttps://github.com/riscv/riscv-v-spec/commit/6f702a213f295206bdc011f9d1c53911242f7261 https://github.com/riscv/riscv-v-spec/commit/6f702a213f29520... The github is never the place to find ratified specs. It was used for the working draft of 1.0, and will be used for the working draft of 2.0. There have already been dozens of commits there post-ratification, mostly clarifications or corrections to the documentation, but in future there will be new functionality.