[llvm] [clang] Remove experimental from Vector Crypto extensions (PR #69000)

https://github.com/4vtomat closed https://github.com/llvm/llvm-project/pull/69000 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[llvm] [clang] Remove experimental from Vector Crypto extensions (PR #69000)

4vtomat wrote: moved to the new [one](https://github.com/llvm/llvm-project/pull/74213) https://github.com/llvm/llvm-project/pull/69000 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[llvm] [clang] Remove experimental from Vector Crypto extensions (PR #69000)

ebiggers wrote: No activity here in a few weeks, so I've opened https://github.com/llvm/llvm-project/pull/74213 with an updated version of the change. https://github.com/llvm/llvm-project/pull/69000 ___ cfe-commits mailing list cfe-commits@lists.llvm

[llvm] [clang] Remove experimental from Vector Crypto extensions (PR #69000)

@@ -141,6 +141,23 @@ on support follow. ``Zve64f`` Supported ``Zve64d`` Supported ``Zvfh`` Supported + ``Zvbb`` Supported + ``Zvbc`` Supported + ``Zvkb`` Supported + ``Zvkg`` Supported + ``Zv

[llvm] [clang] Remove experimental from Vector Crypto extensions (PR #69000)

ebiggers wrote: FYI, I tried squashing the commits of this pull request and rebasing onto `main`, but there are conflicts in several files https://github.com/llvm/llvm-project/pull/69000 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://

[llvm] [clang] Remove experimental from Vector Crypto extensions (PR #69000)

ebiggers wrote: Hi! What's the status of this pull request? Are there any major issues remaining? It would be very useful to have the LLVM assembler officially support the vector crypto extensions. I've been reviewing the [RISC-V vector crypto accelerated crypto routines for the Linux ker

[llvm] [clang] Remove experimental from Vector Crypto extensions (PR #69000)

https://github.com/topperc commented: 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? https://github.com/llvm/llvm-project/

[llvm] [clang] Remove experimental from Vector Crypto extensions (PR #69000)

@@ -106,6 +106,8 @@ static const RISCVSupportedExtension SupportedExtensions[] = { {"zdinx", RISCVExtensionVersion{1, 0}}, +{"zexperimental", RISCVExtensionVersion{1, 0}}, + 4vtomat wrote: No, we don't~ https://github.com/llvm/llvm-project/pull/690

[llvm] [clang] Remove experimental from Vector Crypto extensions (PR #69000)

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 `l

[llvm] [clang] Remove experimental from Vector Crypto extensions (PR #69000)

asb 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 `let RequiredFea