ebiggers wrote:
At
https://github.com/ebiggers/llvm-project/tree/remove_experimental_from_vector_crypto
I've rebased this pull request, squashed the commits, resolved conflicts,
fixed the Zvkn duplication, and run `git clang-format`. Note, it was necessary
to change the type of `enum
4vtomat wrote:
This update add "experimental" to `RISCVFeatures.td`, also add a member
variable `HasExperimental` to record whether the target has this feature.
https://github.com/llvm/llvm-project/pull/69000
___
cfe-commits mailing list
4vtomat wrote:
> Do we need to add the "experimental" feature to RISCVFeatures.td? If the
> feature string shows up in the function attributes, won't the backend print
> that it doesn't recognize the feature name when it parses the string?
Yes, we do, I forgot it lol~
@@ -106,6 +106,8 @@ static const RISCVSupportedExtension SupportedExtensions[]
= {
{"zdinx", RISCVExtensionVersion{1, 0}},
+{"zexperimental", RISCVExtensionVersion{1, 0}},
+
kito-cheng wrote:
I guess we don't really need this dummy extension in
4vtomat wrote:
Since it's possible that **ISA spec** and **intrinsics spec** are not
synchronized, so the updates add an dummy extension called **zexperimental**,
once `-menable-experimental-extensions` is specified, the feature
`zexperimental` is automatically added.
If specifying `let
