4 ms·
And then formalize enough of them that there are now over 1 quintillion valid ways to create a standards-conforming RISC-V core.
by pclmulqdq 2y ago
And then formalize enough of them that there are now over 1 quintillion valid ways to create a standards-conforming RISC-V core.
- snvzz 2y agoNot a concern, as the common ecosystem of binary software follows RVA profiles. Microcontrollers / embedded can go wild, as the vendor controls the whole stack and can build its firmware images to suit the system.
- pclmulqdq 2y agoThe big promise of RISC-V for embedded was that vendors would not have to maintain toolchains like that. There's no real benefit over using a proprietary core if you have to maintain your toolchain. That's a big reason why they use Arm cores.
- snvzz 2y agoAbsolutely, that's why the toolchains (gcc and llvm) support specifying which extensions to use. Most people are gonna build for a profile, but embedded can build for whatever custom set of extensions the core they are using has, which does not have to be a profile.
- cmrdporcupine 2y ago+1. It's a weird thing to complain about considering building for ARM already involves a bunch of board specific compiler arguments in regards to FPU, MMU, etc. If anything, choosing the extension set is cleaner.