3 ms·
It is not different in the sense that my compiler can generate code that runs on RISC-V and runs faster on RISC-V with specific extensions. Binary compatibility
by marcodiego 5y ago
It is not different in the sense that my compiler can generate code that runs on RISC-V and runs faster on RISC-V with specific extensions. Binary compatibility, in practice, is not lost.
- ncmncm 5y agoThere is no requirement to execute instructions defined in an extension not supported. So, it means building for RISC-V is necessarily complicated. Worse, if it traps and emulates instructions, then optimizations using extension instructions become radical pessimizations.
- avianes 5y agoWhatever the target processor is, when we need performance we recompile for that specific target. And whatever the target processor is, if you need portability you compile only with extensions widely used. It's the exact same problem with x86 or arm. So.. yes, currently RISC-V is mostly made of isolated extensions, but the goal is clearly to create groups of extensions that will be widely supported.