[llvm-dev] [RFC] Upstream development of support for yet-to-be-ratified RISC-V extensions

Jacob Lifshay via llvm-dev llvm-dev at lists.llvm.org
Tue Jan 21 07:28:06 PST 2020


On Tue, Jan 21, 2020, 05:01 Alex Bradbury via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> So based on feedback so far, I'd like to narrow the field to:
>
> Option 1)
> * Unratified extensions are not available through the ISA naming
> string and are enabled via `-riscv-experimental-foo` or similar
> * A warning is always emitted when enabling experimental extensions
> * Support is always compiled in, and the flags aren't ifdeffed out
>
> Option 2)
> * Unratified extensions can be enabled by passing a flag like
> -riscv-enable-experimental-extensions and additionally putting the
> extension name and version number in the ISA naming string (version
> number is always required, and we will only accept the 'current'
> version number).
> * A warning is always emitted when enabling experimental extensions
> * Support is always compiled in, and the flags aren't ifdeffed out


Option 2 for me!

Jacob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200121/96308a05/attachment.html>


More information about the llvm-dev mailing list