10 ms·
The real reason RISC-V is succeeding, relative to ARM: If you make your own CPU - With ARM, You have to pay ARM for ISA license (after a several months long n
by snvzz 5y ago
The real reason RISC-V is succeeding, relative to ARM:
If you make your own CPU
- With ARM, You have to pay ARM for ISA license (after a several months long negotiation), and you cannot license your CPU design to anyone, as ARM has the exclusive right to do that with their designs.
- With RISC-V, you get a free ISA license, and you can license your CPU design to others.
If you do not make your own CPU
- With ARM, you can (after a several months long negotiation) license one of the few designs ARM has available. There's no other vendors that can offer you ARM CPU designs.
- With RISC-V, right now, you can license any among hundreds of options available, from tens of vendors. The licensing process is usually very short and straightforward. Alternatively, there are some open hardware designs. You can get commercial support for some of them.
Frankly, unless ARM does radically change their business model, I do not expect them to survive.
- einpoklum 5y agoTheir business model was to be sold to NVIDIA, but that didn't work out. Anyway, that's all well good, but - does anyone end up making decent RISC-V processors that could replace a desktop CPU, or a RPi CPU, or something weaker but not in a small niche? Or is this still a vision for the future?
- snvzz 5y ago>does anyone end up making decent RISC-V processors that could replace a desktop CPU As of November, a large number of extensions got ratified, including the vector extension, cryptography acceleration, hypervisor support and other important features. RISC-V is finally not missing any important feature ARM or amd64 have, and it does it with an order of magnitude lower number of instructions (equivalent but simpler, i.e. better) and with significantly higher code density. However, test chips with the first designs implementing all of that will take time, even assuming they were tapped out right then, after confirming no last minute changes. High performance cores depend on these extensions, so we'll begin to see them soon. We know multiple such efforts exist. Tenstorrent has one such project, led by Jim Keller. >Their (ARM) business model was to be sold to NVIDIA, but that didn't work out. They intend to go public now. I recommend against buying those shares, as I do not expect ARM to turn around.
- thetallstick 5y ago> with significantly higher code density. This is not correct and is a known weakness of RISC-V at the moment. The ARM toolchains are really good and have decades of improvements in them. This is a big issue for those who need to buy ROM in volume. Better tools are coming online though. For example: https://blog.segger.com/code-size-closing-the-gap-between-risc-v-and-arm-for-embedded-applications/ https://blog.segger.com/code-size-closing-the-gap-between-ri... "One of the issues faced by RISC-V developers is that the code density of the RISC-V instruction set for deeply embedded processors does not match that of Cortex-M with existing tools."
- posterboy 5y agoWhat remedie do you recommend against buying those shares, though?
- saagarjha 5y ago> RISC-V is finally not missing any important feature ARM or amd64 have, and it does it with an order of magnitude lower number of instructions (equivalent but simpler, i.e. better) and with significantly higher code density. This has historically been a problem with RISC-V and it’s not really something you’ve backed up as being improved.
- inkyoto 5y ago> […] an order of magnitude lower number of instructions (equivalent but simpler, i.e. better) […] I am not sure how to parse the «simpler, i.e. better» part; simplicity vs betterness is orthogonal at best and is contradictory at worst. Very few people write meticulously handcrafted, highly optimised code for any ISA today, and the compiler writers actually prefer a more complex ISA as it becomes easier for them to transalate high level programming abstractions into an efficient concrete hardware implementation and run it through an optimising pass. Simplicity of the ISA does not immediately translate into faster or more optimised code. Moreover, creating a highly efficient optimiser is no easy feat as it depends on a large variety of factors and the in-depth knowledge of a specific CPU incarnation: the knowledge of each instruction's timing, instruction interdependencies (i.e. the most optimal instruction sequence that does not stall the pipeline or maximises the ALU/whatever utilisation etc etc), L1 I and D cache line sizes, the knowledge of a particular CPU model / generation… – and that is just a beginning. There is a good reason why Intel, AMD, IBM, ARM et al publish hefty optimisation guidelines / documents for each generation of their CPU's with the compiler writers in mind: the same sequence of instructions issued for the CPU model 123 might be less (or more) efficient than in the next CPU model 456 and vice versa; moreover (e.g. specifically for Intel vs AMD), a sequence of instructions optimised for a particular Intel generation might underperform for an equivalent AMD model or vice versa. Same is likely to be true for different RISC-V core designs from different RISC-V vendors. This is the reason why -mcpu=XXX and -mtune=YYY exist in GCC and clang/LLVM: efficient low-level code optimisation is a tricky business and depends on a large number of compounding factors. It remains to be seen how the optimisation will be tackled in the RISC-V case with its potpourri of optional ISA extensions and also with the instruction fusion. Given that a random concrete RISC-V implementation can be a combination of the base ISA + a random permutation of any RISC-V extensions (in the worst case scenario), emitting the code that will run equally efficient across N different RISC-V core designs appears to be problematic. Instruction fusion can pose another challenge as a fused macro-instruction may or may not run as efficiently on a RISC-V instance that does not fuse them. There is no guarantee that the compiler generated / optimised code will be equally highly performant across different implementations even for the same set of ISA extensions.
- vbezhenar 5y agoThere are rumours of Apple being interested with RISC-V. May be MacBook 2030 will feature it.
- snvzz 5y agoApple posted job advertisements looking for RISC-V technical roles. What they plan to do with them is unknown, but Apple has the cash flow to try a lot of things. I would expect them to quickly adopt it for embedded applications, and experiment with making their own high performance design, including porting MacOS and Rosetta Stone. They can afford to do this much, regardless of whether they end up moving their main CPUs to RISC-V or not.
- unfocussed_mike 5y agoYep. There's surely a bunch of uses of RISC-V that have little or nothing to do with the main CPU, even in a conventional machine. Trust modules, device controllers, smart adapter cables etc.
- jhickok 5y agoFor what it's worth, Apple always has people on hand monitoring innovations in technology and testing their stack on new hardware, most of which never sees the light of day.
- Macha 5y agoSee OS X on Intel being a thing inside Apple for years and years before they decided it should see the light of day.
- throwawayboise 5y agoNEXTSTEP was multi-architecture even before Apple owned it.
- m463 5y agoI would imagine apple actually ships hundreds of devices with processors - each dongle and peripheral has at least one.
- PaulHoule 5y agoMy take is that RISC-V is not that great of an architecture and might never compete at the high end. (e.g displace ARM, Intel, POWER, etc.) On the other hand there is a vast market for low-end CPUs that have specializations to be disk controllers and things like that. If the ISA and all the IP required to make specialized devices is free and particularly if there is a culture in which it is easy to learn how to do that then RISC-V will have a special place. My next spatial computing project is going to be RP 2040 based mostly because I have the parts in stock (other projects are blocked because of supply chain issues) but I am really an AVR8 fanatic and the only path forward I see to higher performance AVR8 systems is a soft core running on an FPGA where very hard tasks (vision? comms?) get offloaded to the FPGA and that can be a very appealing architecture where somebody might prefer RISC-V particularly if the tooling and accelerator integration are there.)
- zozbot234 5y ago> might never compete at the high end. (e.g displace ARM, Intel, POWER, etc.) It might also be successful, even in that segment. The RISC-V ISA was specifically designed to scale up (e.g. to OOO and vector processors) while still being very simple, especially at the low-end - a basic RV32E is really comparable in complexity with many real-world 8- and 16-bit chips.
- jabl 5y agoThe pretty minimal RV32EC core Ibex is estimated 15k gates: https://github.com/lowRISC/ibex https://github.com/lowRISC/ibex But, the similarly minimal Arm Cortex M0 is, drumroll, 12k gates. Not saying this means Arm is better than RISC-V, such a small difference can probably be explained by some microarchitectural feature or lack of it. Just that you can scale down Arm as well. But yes, I can see tiny chips like these putting a squeeze on 8 and 16 bit microcontrollers.
- snvzz 5y ago>My take is that RISC-V is not that great of an architecture That's not the impression I got, when I studied the specification. Do you care to elaborate?
- rjsw 5y agoMaking a RPi equivalent would require a GPU with Linux support, I don't see any sign that RISC-V chip vendors are able to do this. Building a desktop system with a PCIe graphics card would be easier.
- Narishma 5y agoIsn't Imgtec doing that?
- rjsw 5y agoWhere can I get the source code for PowerVR kernel drm code from?
- snvzz 5y agohttps://www.phoronix.com/scan.php?page=news_item&px=Open-Source-PowerVR-Vulkan https://www.phoronix.com/scan.php?page=news_item&px=Open-Sou...
- Narishma 5y agoNowhere because it's not available yet. They only made a few announcements.
- snvzz 5y agoThis has since changed. They've released a DRM/DRI driver.
- ColonelPhantom 5y agoThere actually exists at least one GPL-licensed GPU core (GPLGPU), but it's based on a 90s PC 3D accelerator that's really just not that good. I believe the team behind LibreSOC is also working on a 3D processor, but I don't know how far along they are. However, if a vendor instead ships a decent framebuffer and high-performance vector unit, I think LLVMpipe would not be a problem for most RPi-equivalent use cases, either light desktop use or server use (especially the latter!)
- hajile 5y agoJim Keller's team is creating a 6-wide issue RISC-V CPU. It should have similar IPC as ARM X1 or AMD Zen 3. https://youtu.be/KOHQQyAKY14?t=494 https://youtu.be/KOHQQyAKY14?t=494
- Taniwha 5y agohere's an 8-issue design: https://moonbaseotago.github.io/ https://moonbaseotago.github.io/
- gumby 5y ago> Frankly, unless ARM does radically change their business model, I do not expect them to survive. I kind of agree, but it’s not straightforward. ARM’s growth wasn’t so much a hockey stick as a more continuous curve with a small exponent. Yes, they only started in 1990, but that was itself a reboot/restart after acorn’s 12 years of effort. And they were scrambling hard for every deal for at least another 15 years. The environment in which RISC-V emerged is different, of course, but many of the dynamics are still the same. Car companies were still using 16 and even 8 bit devices into the 21st century. Secondly, ARM has a large arsenal of patents that go along with the license, and they continue to add to the load. I bear ARM no ill will but I also want RISC-V to supplant them. I just don’t think it’s automatic.
- yywwbbn 5y agoAnd if ARM started allowing everyone to use their IP for free you would expect them to survive? ARM the architecture might survive but probably no ARM the company. IMHO a more likely outcome with Risc (assuming it gets widely adopted) would be one or two companies like Samsung, Qualcomm, AMD or even Intel gaining a massive advantage and profiting from it instead of cheaply licensing their designs to other companies. I don’t really see how is that preferable to the ARM model where company can theoretically license the most advanced ARM cores there are (of course aside of what Apple is doing) or mostly equal terms. Of course RISC might push them to make their licensing mechanism to be more flexible if they start considering RISC an a real threat to them (I don’t think this is very likely to happen in the near future, though)
- snvzz 5y ago>if they start considering RISC an a real threat to them I'm afraid they have seen RISC-V as a threat for a while now. It has already been years since their first FUD campaign. >if ARM started allowing everyone to use their IP for free you would expect them to survive? That's not how I see ARM surviving. One way ARM could survive is by doing what the MIPS owners did: Abandon the ISA, move to RISC-V, use your extensive expertise to make competitive cores, and your clout in the market to sell them to your pre-existing clients. They could totally pull it off, but it would honestly surprise me if they did so, considering how poorly they've dealt with RISC-V so far.
- Someone 5y ago> The way ARM could survive is by doing what the MIPS owners did: Abandon the ISA, move to RISC-V, use your extensive expertise to make competitive cores, and your clout in the market to sell them to your pre-existing clients. Even if that’s their best bet, long term, I don’t see why they would have to start doing that right now. Why would they leave their castle with its golden egg-laying goose, only because they know it won’t live for X more years? Timing such transitions is always difficult (you can’t wait until your goose is dead), but I think they’re better of waiting at least a few more years. The MIPS owners were in a different situation, weren’t they? Their goose already was dying or even dead.
- klelatti 5y agoThis all rests on the several suppositions including: - Arm has no IP that can’t be quickly replicated by other firms (for very little money). - That the quality of designs from other firms will be better than those from Arm (or for the architecture licensees their own). - The really big Arm licensees would see a commercial advantage to switching. Intel threw billions at the smartphone market and still lost against Arm. Today there are zero RISC-V smartphone designs. That may change but probably largely because of the Arm China and Nvidia missteps. I expect (and look forward to) RISC-V establishing a presence in the market but this sort of commentary does the ISA no favours. Edit: I see elsewhere you think they should abandon the Arm ISA in favour of RISC-V! really not sure about that ..
- renox 5y ago1) Intel is/was handicapped by using an old CISC ISA which has some cost in power/performance. This complex x86 decoder ain't free. 2) Network effect favoured ARM.
- klelatti 5y agoIntel also had the advantage at the time of a clear process advantage which almost certainly would have more than offset the decoder cost.
- darksaints 5y agoI think the real value isn't so much to do with the Free-As-In-Beer aspects, and more to do with the Free-As-In-Freedom aspects. Having so much open documentation and off the shelf capabilities is like a superpower, and you're starting to see it with stories like these: https://riscv.org/blog/2020/11/13-year-old-nicholas-sharkey-creates-a-risc-v-core/ https://riscv.org/blog/2020/11/13-year-old-nicholas-sharkey-... We've got kids designing their own cores. That was a bar that previously was out of reach to anybody without a nine-figure engineering payroll. That's amazing.
- mhh__ 5y agoNot really, students have been designing RISC cores as long as RISC has been around. It's a standard exercise. RISCV does make it a bit easier and gives you a clean ISA but it hasn't really had that much of an influence due to its own design i.e. it's caused people to herd around it so there's lots of tutorials and work to borrow floating around.
- Symmetry 5y agoHaving a relatively sophisticated core you can take off the shelf and modify for your own research can be incredibly useful in academia, I would have really liked that when I was doing my thesis. For large companies too who might want particular new instructions or sets of features that are best suited to their own use cases.
- jlokier 5y agoSPARC has been open source since 2005, complete with high quality implementation released in 2006. 64-bit, 8 cores, 32 hyperthreads, rising to 64 by 2007. Simulator also provided. SPARC was able to run Linux and Solaris, and used by Sun in their servers that powered much of the commercial internet in late 90s and early 2000s (before x86 Linux took over). There have been a few others since then. So relatively sophisticated open source cores for study and modification have been around for many years by now. It looks to me like the difference with RISC-V is that a larger community has formed around it due to smart organisation and the timing being right, rather than availability.
- mhh__ 5y agoIf it becomes an issue ARM probably will change dramatically, however keep in mind RISC-V let's you licence hundreds of probably pretty crummy cores (and a handful of good ones) whereas ARMs are battle tested, verified, and come with documentation. RISC-V docs are still a bit 1980s i.e. as far as I'm aware there's no official online source of HTML docs, and not as much blessed software as arm (i.e. compilers tested in-sync with the ISA). Oh and people to sue... I also trust the ARM ISA designers more than the RISC-V ones, but I don't know enough that you should trust me.
- klelatti 5y agoI'm sorry to say there does seem to be a certain lack of respect for the Arm ISA designers floating around. Arm v8 is in billions of smartphones and powers the core with the fastest single threaded performance out there, but somehow it's obviously inferior and will be supplanted.
- mhh__ 5y ago> I'm sorry to say there does seem to be a certain lack of respect for the Arm ISA designers floating around. I was going to use that exact wording in a different comment but decided against it, spooky
- klelatti 5y agoThat is spooky! I mean there was clearly a lot of analysis put into aarch64 - which probably involved Apple etc - but I've seen comments previously saying they obviously got it wrong because [insert some headline design decision]. They might have got it wrong but they're definitely not amateurs at this and you can't prove anything with a one line comment.
- ignoramous 5y agoI guess the point is, given the eye balls RISC-V is going to attract, you'd have your Tencents and Apples of the world pouring resources into it, just like they did with AARCH64. And when that happens, where does ARM, as a company, go? They did to Intel what RISC-V is poised to do to them, may be in a decade or two. I feel ARM could go the Docker way, who faced a similar foe in the stakeholders seeking to commoditize their core business... ruthlessly stomped on them, creating k8s, runc, registries, microvms, serverless, and what-not. Despite Docker having stellar engs working for them (and in some cases, better tech: Swarm, for instance), there's nothing they could do.
- MayeulC 5y agoAlso, waiting for IP is a huge bar for entry. Suppose you just want a soft core for a one-off FPGA project. RISC-V is a no-brainer if you need to run complex stuff like a Linux kernel. There's myriad of projects to pick from on GitHub. Try them all, pick the one you prefer. The barrier to entry is so much reduced that you can use RISC-V "by accident" without having considered it in advance, as part of a normal engineering process in companies of any size, vs months-long waits for IP, after deciding it was worth obtaining.
- kllrnohj 5y ago> Frankly, unless ARM does radically change their business model, I do not expect them to survive. Survive what? I don't see RISC-V disrupting much of ARM's bigger-named business (eg, phones, with some inroads into other things like Apple Silicon & laptops). Maybe Amazon pivots into RISC-V for the next Graviton? But that also seems unlikely unless someone with very deep pockets invests in making an actually competitive RISC-V CPU core at the mid/high end. ARM's low-end market seems likely to be taken over by RISC-V. So like the Cortex M series days seem numbered without a change in the business model. But that seems like about it.
- webmaven 5y ago> ARM's low-end market seems likely to be taken over by RISC-V. So like the Cortex M series days seem numbered without a change in the business model. But that seems like about it. Doesn't that inevitably set up a classic Innovator's Dilemma?
- kllrnohj 5y agoI don't think so. ARM may just not care about losing that market. The CPUs they design at that ultra-low-end really don't carry over into the mid & high ends, which is where the high profile design wins & "high" (relatively) margins are anyway. Like what makes for a good hard drive controller doesn't really have anything at all to do with what makes a good smartphone CPU. So RISC-V winning at hard drive controllers or other (tiny) embedded usages is not really setting up an "S" curve for explosion here to challenge ARM's markets. They are really fundamentally different markets & products. Kinda like how Intel just never cared about going after embedded, and they're not exactly struggling as a result of that. With the big asterisk of smartphones where scaling up proved a quicker path to shipping than scaling down, at which point inertia took over, but for that to repeat would require a currently unknown new product category.
- webmaven 5y agoI'd bet on AR glasses that somehow need to squeeze the compute power of a midrange cellphone into the form factor of a pair of glasses.
- thetallstick 5y agoNothing in life is ever simple... > With ARM, You have to pay ARM for ISA license This is only true for some definitions of ARM. See for example: https://en.wikipedia.org/wiki/Amber_(processor) https://en.wikipedia.org/wiki/Amber_(processor) "The Amber core is fully compatible with the ARMv2a instruction set and is thus supported by the GNU toolchain. This older version of the ARM instruction set is supported because it is not covered by patents, and so can be implemented with no license from ARM Holdings" > Frankly, unless ARM does radically change their business model, I do not expect them to survive. Looks like someone is having similar thoughts inside ARM. https://hackaday.com/2018/10/02/free-arm-cores-for-xilinx-fpgas/ https://hackaday.com/2018/10/02/free-arm-cores-for-xilinx-fp... There are other efforts too.