I've released version 0.91 of the RISC-V Bitmanip Spec a few days ago. https://github.com/riscv/riscv-bitmanip/blob/master/bitmanip-0.91.pdf … We added two new instructions, GORC and BFP, and changed the encodings of GREV and BMATXOR. The riscv-bitmanip branches of GNU tools and Spike already support the v0.91 bitmanip spec.
-
Intel at least has the excuse of history for their fragmented instruction sets, but this seems to be setting things up for fragmentation *from the start*.
Yes, because for stuff like ternary instructions it's either making them optional, or not standardizing them at all. And given these two options, I'd prefer having a standard encoding and semantic over everyone re-inventing their own custom conditional move and funnel shift.
-
-
Aha. You are making the "perfect is the enemy of the good" argument here, which sounds reasonable. In an ideal world there would be a minimal yet wonderfully complete set that everyone agrees on, and is somehow not too painful for the leanest of implementations... :-)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.