Craig Maloney ☕ ✅ is a user on octodon.social. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

ARM Limited launches a website and FUD campaign against #RiscV.

Risc-V must have potential in order for ARM Limited to feel the need to "warn" consumers. phoronix.com/scan.php?page=new

Craig Maloney ☕ ✅ @craigmaloney
Follow

@satchmoz "there is the risk of fragmentation with this open-source ISA"

Coming from ARM I find that just a teensy bit disingenuous. :)

· Web · 4 · 11

@craigmaloney @satchmoz As a member of the RISC-V mailing lists (ISA, hw-dev, and sw-dev specifically), this statement is true, on several levels.

First, people looking to commit implementations to silicon aren't going to wait for the standards process to arrive at an ideal ISA for, e.g., crypto. They're going to add their instructions, spin the glass, and then go back and retrofit their ISA later *IF* it's deemed important enough. This has already happened.

@craigmaloney @satchmoz Then there are people like myself who made their own RISC-V core in Verilog or whatever, and observe the specs are becoming too complicated to follow for FPGA-based designs. I've already announced my intention to fork due to over-bearing complexity. From this frustration came the recognition that small MPUs have very different needs, and proposals are on the table for addressing their needs specifically. Sifive's CLIC core is a good example of what's come from it.

@craigmaloney @satchmoz So, yes, fragmentation has already happened. And it will continue to happen, as applications become more diverse and/or complex and/or resource constrained.

@craigmaloney @satchmoz Personally, my estimation is that this is healthy. I've **NEVER** liked the ITU-style standards-setting process that the RISC-V foundation has adopted. It leads to onerous standards. I find the IETF-model more applicable, where you have at least two compatible yet different implementations in hand before you even are allowed to write the RFC.

As long as communications between groups remains vibrant and healthy, RISC-V has nothing to fear from fragmentation.

@vertigo @craigmaloney I don't think @craigmaloney doubted RiscV could fragment, just that Arm itself is already littered with similar issues.

@satchmoz @craigmaloney I am in agreement here; but wanted to add my first-hand anecdotal evidence that fragmentation isn't just normal, it's necessary for the project to evolve at a healthy pace.

Plus, the negative effects of fragmentation seems to be bounded nicely in proportion to the degree that people communicate things on the mailing lists. I don't know to what degree ARM allows for such communications, but with RISC-V at least, it's encouraged.

@satchmoz @vertigo Oh absolutely; My main concerns with RISC-V are that it will fragment and none of the work will make it back upstream. But for ARM to claim some form of high ground in fragmentation makes me want to roll my eyes. :)

@craigmaloney @satchmoz But it's totally a single ISA, just with different profiles 😹