Displaying 2 results from an estimated 2 matches for "rv32imafdc".
2020 Jan 16
7
[RFC] Upstream development of support for yet-to-be-ratified RISC-V extensions
...# Proposal
Although we want to discourage downstream reliance on unratified extensions,
there doesn't seem to be a strong motivation for requiring a custom LLVM build
to force this. However, such unratified extensions shouldn't be accessible via
normal RISC-V ISA naming strings (e.g. "rv32imafdc"), and instead flags of the
form `-riscv-experimental-vector-ext` in LLVM and `-mexperimental-vector-ext`
in Clang should be used (i.e. option 3)). We discussed this in our weekly call
however, and there were voices advocating either option 2 or 3. Input welcome.
If going down the option 3 ro...
2020 Jan 21
6
[RFC] Upstream development of support for yet-to-be-ratified RISC-V extensions
...o discourage downstream reliance on unratified extensions,
> > there doesn't seem to be a strong motivation for requiring a custom LLVM build
> > to force this. However, such unratified extensions shouldn't be accessible via
> > normal RISC-V ISA naming strings (e.g. "rv32imafdc"), and instead flags of the
> > form `-riscv-experimental-vector-ext` in LLVM and `-mexperimental-vector-ext`
> > in Clang should be used (i.e. option 3)). We discussed this in our weekly call
> > however, and there were voices advocating either option 2 or 3. Input welcome....