[PATCH] D109215: [RISCV] Fix arch sring parsing for multi-character extensions

Yueh-Ting Chen via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Fri Sep 3 02:28:38 PDT 2021


eopXD added a comment.

In D109215#2981746 <https://reviews.llvm.org/D109215#2981746>, @jrtc27 wrote:

> RISC-V manual, §27.6:
>
>> Standard extensions can also be named using a single “Z” followed by an alphabetical name and an optional version number.
>
> Numbers are not in the alphabet, therefore they cannot be part of a valid name. If you start allowing numbers in the extension name then this introduces the need for all kinds of weird edge cases to remove ambiguity, but leads to huge amounts of confusion. Just don't do it.

Hi Jessica,
I was told that upcoming rvv sub-extensions will contain digits in the extension name. (see the v1.0-rc1 <https://github.com/riscv/riscv-v-spec/blob/master/v-spec.adoc#181-zvl-minimum-vector-length-standard-extensions>).
`zvl*` and `zve*` would be appended as architecture names inside `-march`. 
Therefore I think your concern should be raised as an issue there?


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D109215/new/

https://reviews.llvm.org/D109215



More information about the llvm-commits mailing list