4 ms·
I am seeing more and more of what look like viable alternatives to RISC-V. Agner Fog has an ISA with vector instructions that should influence all future design
by ncmncm 7y ago
I am seeing more and more of what look like viable alternatives to RISC-V. Agner Fog has an ISA with vector instructions that should influence all future designs. The Bitmanip extension to RISC-V is likewise an education, and should inform any future designs.
RISC-V itself? The core design seems very academic. Seriously, who omits rotate instructions?
- Taniwha 7y agoSomeone trying to minimise gate counts (a full barrel-shifter is an N squared sort of thing) People forget that RISC comes out of researchers doing analysis of instruction use, and removing stuff you don't use much - if you can bump the clock speed by 5% by halving the size of a full barrel-shifter then you can execute more instructions per second even if you have to use 3 to do a rotate
- sifar 7y agoROT (and shifts) is N log N. Look at shuffle networks. If you have shift operations in the core, their is no reason you cannot have a ROTATE operation. It doesn't add much additional HW.
- Taniwha 7y agoit adds to gate delays (especially when N is 128 - a 128 fan in is pretty expensive in space and time)
- CalChris 7y agoYeah, RISC-V omitted rotate from its 47 instruction base ISA. You don't get to be that small without cutting the unnecessary and rotate would require a barrel shifter which in turn would rarely be used. Instead, rotate (rol, ror, rori) can be found in the “B” Standard Extension for Bit Manipulation.
- ncmncm 7y agoRotation costs exactly the same to implement as shifting, and shares the same hardware, so has about zero marginal cost. "Academic."
- microcolonel 7y agoAn "academic" design is better than the armchair design of somebody who doesn't know how barrel shifters are implemented. Sure, you could microcode it, but are the instructions really that big?
- deleted 7y ago[deleted]
- sifar 7y agoThe parent is right. The HW is not much different. You don't need to microcode them.
- microcolonel 7y agoIf you don't have a barrel shifter in your design, but your design is microcoded, you may choose to implement a rotate with a few μops, much the same way that you would write it in software.
- drudru11 7y agoThey are trying to be big and small. When the Intel dropped its barrel shifter, they caught a lot of hell for the massive performance hit. They promptly re-included it in processors following the P4.
- sifar 7y agoViewing it from the other side, when you split some of the useful but different operations into a bunch of orthogonal extensions, then when you have to do something really useful, you have to implement the entire extension. That equally bloats your core. In this case, one cannot just implement ROT, one has to implement the entire Bit manipulation extension. Scale it up across the extensions - say you need 3 basic ops from 3 different extensions. Sure you can add your custom ROT op, but then you end up breaking compatibility. [Edit] The principle of removing unused/rarely used HW goes for a toss since now you have a bunch of operations from these extensions that would lie unused yet consume HW. It is not the basic operations that cause bloat, it is the functional variants - need to support different width, indexing, different constant. In this case shift and rotate have the same function. Immediate ones are the variants.
- zamadatix 7y agoThat ROT is 3 instructions rather than 1 on the absolute base RISC-V design is the most common criticism I see of RISC-V on HN bodes well that it is a good design.
- sifar 7y agoPeople are adopting RISC-V not because it is an order of magnitude better ISA, but it frees them from vendor lock-in. Whether it is the one good design to rule them all, we'll only be able to tell after a decade or two when the computing/tech world has moved on to different applications. For e.g. what happens when 128b register widths become the norm ? I suspect the base core and may be the FPU will remain relevant (because by then it would be legacy with vast amount of software base), however the other extensions will be superseded/replaced. This will lead to managing the extensions with conflicting encoding like one has to manage different SW library versions.