2 ms·
Sure, but as I understand it RISC-V was not intended to be used for big high performance general CPUs. It’s specifically optimised for small core applications,
by simonh 6y ago
Sure, but as I understand it RISC-V was not intended to be used for big high performance general CPUs. It’s specifically optimised for small core applications, with extensions allowing efficient support for only the additional functionality needed for a specific product. Complaining that RISC-V isn’t well suited to designs competing with Snapdragons and M1 is somewhat missing the point.
There has been some talk of a breaking fork of RISC-V better suited to large high performance designs. I think that makes a lot of sense and would allow RISC-V to stay good at what it was intended for.
- andrewflnr 6y agoPlease tell me they're calling it RISC-VI.
- jleahy 6y agoRight, but the OP and most of HN seem to believe that RISC-V is some magic thing that is going to beat M1/Zen/whatever one day while also providing amazingly low power for tiny 32-bit cores. Also, RISC-V is also essentially split into two incompatible instruction sets (32-bit and 64-bit, even if you forget the huge amount of extensions). It would have been better just to design two completely separate instruction sets (32-bit for low power, 64-bit for high performance), but at core it's a teaching instruction set like MIPS before it, so they went for simplicity not optimality.