3 ms·
Yes, only standard extensions will be supported by all compilers. Why is this a problem? If a company needs to design its own extension for its specific appli
by avianes 6y ago
Yes, only standard extensions will be supported by all compilers.
Why is this a problem?
If a company needs to design its own extension for its specific application, RISC-V allows it.
And it will never get upstream, because it is only relevant for this specific application.
And if this application is needed by many vendors, then it means that a standard extension must be designed.
- pjmlp 6y agoThink Android, but RISC-V ISA instead.
- afiori 6y agoAndroid is not fragmented, it is easy to write applications that run well on all android versions. The problem RISC-V faces is that one or more companies start to grow a significant market with non-compliant chips, basically the browser war scenario.
- pjmlp 6y agoSaid the one that never had to deal with background activities or firmware issues across the eco-system.
- afiori 6y agoyep, that is me, I thought that the main issues were around deprecated features in newer API versions, I guess I was wrong.
- avianes 6y ago> The problem RISC-V faces is that one or more companies start to grow a significant market with non-compliant chips, basically the browser war scenario. The CPU market today is even more closed to competition than web browsers. RISC-V does not "face this problem", this problem already existed before RISC-V. But RISC-V could make this market more competitive. If there is a royalty free standard on top of which all modern CPUs are built (the RISC-V ISA), then a newcomer can easily use it and take advantage of the tools which go with it. But companies remain free to diverge from this standard by adding their own non-standard extensions.