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
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
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
@@ -141,6 +141,23 @@ on support follow.
``Zve64f`` Supported
``Zve64d`` Supported
``Zvfh`` Supported
+ ``Zvbb`` Supported
+ ``Zvbc`` Supported
+ ``Zvkb`` Supported
+ ``Zvkg`` Supported
+ ``Zv
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://
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
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/
@@ -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
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
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
4vtomat wrote:
> Thanks for the patch, some very quick feedback and I'd highlight the first
> bullet as the most important, as this is potentially a blocker for graduating
> these extensions from experimental.
>
> * My big concern with this would be the intrinsics - could you please comment
>
github-actions[bot] wrote:
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
You can test this locally with the following command:
``bash
git-clang-format --diff ba79fb2e1ff7130cde02fbbd325f0f96f8a522ca
521060552794304a5f6b31e38c25ab0a7a0353ff --
asb wrote:
Thanks for the patch, some very quick feedback and I'd highlight the first
bullet as the most important, as this is potentially a blocker for graduating
these extensions from experimental.
* My big concern with this would be the intrinsics - could you please comment
on the status o
13 matches
Mail list logo
