Exactly that. Take your source code and it should compile and run on any RISC-V chip - just as it should run on any other chip.I see RISC-V as a way for multiple hardware vendors to create processors that are all part of the same software ecosystem.
This allows programmers a guaranteed return on investment when creating and optimising RISC-V software as it can run on hardware from multiple manufacturers. Manufacturers benefit by having a mature software ecosystem ready to go.
But just as we need separate compilers for code which runs on a Pi and code which runs on a Pico, have to edit that Pi code before the Pico SDK will compile it, it's not always the utopia one would like.
RISC-V allows various extensions and, while a single compiler could support all the public options, manufacturers are allowed to add proprietary extensions which will require proprietary compilers.
Some mark RISC-V down for that, note there is a risk of fragmentation, but I don't see it as any worse than how things are already.
It's not likely a problem for hobbyists, makers and programmers targetting RISC-V desktops and laptops which won't use proprietary extensions. It shouldn't be a problem for industrial developers who do because jumping through hoops comes with the territory. Those who do want to use proprietary extensions will have to suck it up just as those developing for RP2 have to.
Statistics: Posted by hippy — Thu Jul 24, 2025 12:08 pm