News for hackers. Stuff that matters.
Re:How to improve the RISC-V specification by drycabinet on Sunday April 28, 2024 @12:03AM (#40185891)
Is RISC-V technically superior or is it just about the license?
Re:How to improve the RISC-V specification by __s on Sunday April 28, 2024 @12:23AM (#40185971)
It's simpler than x86/arm, while having a couple improvements compared to minimal alternatives like MIPS based on hindsight & modern chips

See chapter 2: https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-...

Re:How to improve the RISC-V specification by gchadwick on Sunday April 28, 2024 @01:20AM (#40186197)
ISAs are complex things so you can't say one is technically superior to the other.

I would say you're right though in that RISCV enjoys the success it's seeing due to the open specification and licensing model. People generally aren't drawn to RISCV because of technical innovation.

Re:How to improve the RISC-V specification by brucehoult on Sunday April 28, 2024 @03:14AM (#40186673)
The base specification (IMAFDC) has little to no innovation, simply avoiding the mistakes of the past. We've got 60 years of experience with RISC-style instruction sets, so that's about consolidation not innovation.

However RISC-V is an excellent base upon which to innovate. You can see that in things such as the Vector extension, the memory model developed by industry and academic experts world-wide, and CHERI fine-grained memory-protection.

Re:How to improve the RISC-V specification by fanf2 on Sunday April 28, 2024 @10:12AM (#40188721)
CHERI was originally based on MIPS, then ported to ARM and later RISC-V.
Re:How to improve the RISC-V specification by brucehoult on Sunday April 28, 2024 @06:28PM (#40192556)
The place you can get a real physical commercially available CHERI implementation is RISC-V:

https://codasip.com/press-release/2023/10/31/codasip-deliver...

That's largely because if you base a product on Arm or MIPS you have the choice of getting them to actively invest in and support you, or getting sued into oblivion by them.

THAT is why RISC-V is the most friendly ISA to innovation and where most future innovation will happen. Because innovation comes not only from internally inside Intel or Arm or MIPS (who have switched to RISC-V now anyway) but from a myriad of possible sources.

Re:How to improve the RISC-V specification by rwmj on Sunday April 28, 2024 @05:09AM (#40187160)
The base RISC-V tends to avoid innovation, because we've been burned in the past (register windows, branch delay slots etc)
Re:How to improve the RISC-V specification by DeathArrow on Sunday April 28, 2024 @02:33AM (#40186490)
Superior in what way? Is English superior to French? I think you can have equally good implementations of modern CPUs regardless of the ISA. The end result is trillions of logical gates that working together will store, add, subtract, multiply at a rate of several millions per second. Logical gates don't care what language you speak to them as long as they understand.
Re:How to improve the RISC-V specification by goodpoint on Sunday April 28, 2024 @05:54AM (#40187359)
It's waaay more modern than other ISAs in its design. It can scale from microcontroller to simple CPU to GPU-like vector processing to very powerful CPUs without having to add thousands of CISC instructions.

E.g. The ISA is modular. You can use the RV64GC set of instructions to implement a very basic Linux-capable CPU that executes one instruction at a time.

Then you can build an advanced CPU that does OOO and instruction compression and run the same binary *efficiently*.

Re:How to improve the RISC-V specification by zik on Sunday April 28, 2024 @06:25AM (#40187473)
This article's just about the technical writing of the manual. It's nothing to do with the ISA itself.
Re:How to improve the RISC-V specification by RetroTechie on Sunday April 28, 2024 @12:44PM (#40189843)
It's designed with the luxury of hindsight on longtime-existing ISAs. Avoiding many pitfalls in those. While not attempting to innovate in ways that may or may not work out.

Also the base ISA is very implementer-friendly. As in: requiring few transistors / FPGA LEs, (relatively) easy to write a compiler or emulator for, etc. But that is hardly unique.

32b and 64b flavours very similar. Oh and... modular.

That doesn't make it 'better' though. Eg. x86 has a looott of legacy cruft. But also a looott of high-quality software for it. RISC-V: many of those tools are still being written / adapted / optimized. Likewise, x86 & ARM have many high-performance, efficient and/or low-cost implementations. RISC-V is catching up quickly, but not (yet) head-to-head with those.