3 ms·
Me, I'm ready to see a Risc-6 fork. By keeping most of the details, and just fixing certain unfortunate early choices, it could benefit from almost all the work
by ncmncm 6y ago
Me, I'm ready to see a Risc-6 fork. By keeping most of the details, and just fixing certain unfortunate early choices, it could benefit from almost all the work done on RISC-V, but outpace it in performance.
RISC-V embodies many unnecessarily weird and costly choices that would be easy to patch if you were not obliged to retain bitwise compatibility. At the same time, it benefits from a great deal of verification work that could itself be retargeted relatively cheaply, and applied to the forked ISA. Similarly, implementations could be forked with minimal effort, and get a very cheap performance boost. Compiler code generators would also be easy to fork.
Pretty comprehensive lists of small but costly design booboos have already been published.
Probably the biggest fundamental problem in the RISC-V world is the extensions architecture, where each huge extension effectively holds hostage its few most valuable instructions.
For example, the base instruction set lacks the extremely valuable POPCNT instruction. You don't get it without swallowing the whole, huge B extension, which itself has not even been finalized. Likewise ROTL/ROTR, essential in hashes and crypto. Even multiplication is missing from the base set, unavailable without a lot of other stuff.
Freedom to fork is one of the great benefits of the Free Software movement. The same kind of benefits should be possible for a forked ISA.
Really, network benefits can accumulate for two or more related ISAs as well as for just one, if no corporate walled garden prevents it.
- zozbot234 6y ago> For example, the base instruction set lacks the extremely valuable POPCNT instruction. You don't get it without swallowing the whole, huge B extension, which itself has not even been finalized. You can make a processor implementing the RISC-V base instruction set plus standard popcnt. It won't be a full implementation of the B extension, but as long as it's 100% forward-compatible with one there no issue that I'm aware of.
- ncmncm 6y agoYou can, but this amounts to a fork of RISC-V that does not fix its numerous small but expensive design flaws. As such, it is a fork not attractive enough to evoke a compiler code-generator fork, or an FPGA implementation variant, or to attract users. That's fine for your on-off product, but does me no good. To get all the benefits we expect from the open ISA design, we need enough network effects to amortize the work of maintaining it. It is a fine point to choose how far to go in the fork. Too close, and it's not worth doing. Too far, and work on RISC-V doesn't help it too. For example, a close-enough fork can be verified by demonstrating that each delta is exactly as correct as the corresponding RISC-V feature, by simple mapping.
- deleted 6y ago[deleted]
- avianes 6y agoWhat you say is wrong in many ways. You are talking about forking the project even though the spec is not yet finished and the project is open source and open to participation. Instead of forking, just let the RISC-V team know what the problems are. > Pretty comprehensive lists of small but costly design booboos have already been published. But published by whom? Nowadays it's a great game for all the people who think they're hardware gods to say that RISC-V has big problems. However, most of the time this is due to a lack of understanding or knowledge of the field. For example, the article from the man who calls himself an ARM former employee. But he was neither a core designer nor a core architect, he was in charge of the verification of the core. To verify a core you don't need to understand all the internal workings and why it's designed this way, you are not a core architect. And in fact there is a lot of incomprehension in the criticism he makes. So in order for your criticism to be valid, you must make it clear which error list you are talking about. Otherwise we just can't answer your argument. > You don't get it without swallowing the whole, huge B extension, which itself has not even been finalized. How is the fact that the extension is not finished a valid criticism? In addition, extension B is currently divided into several sub-extensions Z. Including Zbb which contains the rotation, bitcnt, and some logical operation. So RISC-V already addresses the problem you are mentioning. > Even multiplication is missing from the base set, unavailable without a lot of other stuff. The fact that multiplication is not in the base instruction set is a feature, not a issue. And the fact that multiplication comes with division is indeed questionable, but a RISC-V M core can be designed without implementation of division and implement the division in software. The RISC-V spec is designed to allow trap on non-implemented instructions. And we can tell the compiler not to use the division instruction with the flag "-mno-div" on gcc. I think that RISC-V potentially has some small issues. But they are not that serious. And these are none of your criticisms.