On 12/14/23 17:14, Christoph Müllner wrote:
On Fri, Dec 15, 2023 at 12:36 AM Jeff Law wrote:
On 12/14/23 02:46, Christoph Müllner wrote:
On Tue, Jun 20, 2023 at 12:34 AM Jeff Law via Gcc-patches
wrote:
A handful of the scalar crypto instructions are supposed to take a
constant
On Fri, Dec 15, 2023 at 12:36 AM Jeff Law wrote:
>
>
>
> On 12/14/23 02:46, Christoph Müllner wrote:
> > On Tue, Jun 20, 2023 at 12:34 AM Jeff Law via Gcc-patches
> > wrote:
> >>
> >>
> >> A handful of the scalar crypto instructions are supposed to take a
> >> constant integer argument 0..3
On 12/14/23 02:46, Christoph Müllner wrote:
On Tue, Jun 20, 2023 at 12:34 AM Jeff Law via Gcc-patches
wrote:
A handful of the scalar crypto instructions are supposed to take a
constant integer argument 0..3 inclusive. A suitable constraint was
created and used for this purpose (D03), but
On Tue, Jun 20, 2023 at 12:34 AM Jeff Law via Gcc-patches
wrote:
>
>
> A handful of the scalar crypto instructions are supposed to take a
> constant integer argument 0..3 inclusive. A suitable constraint was
> created and used for this purpose (D03), but the operand's predicate is
>
Ping. With RISCV tag this time.
Forwarded Message
Subject: [PR target/110201] Fix operand types for various scalar crypto
insns
Date: Mon, 19 Jun 2023 16:34:28 -0600
From: Jeff Law
To: gcc-patches@gcc.gnu.org
A handful of the scalar crypto instructions are supposed
A handful of the scalar crypto instructions are supposed to take a
constant integer argument 0..3 inclusive. A suitable constraint was
created and used for this purpose (D03), but the operand's predicate is
"register_operand". That's just wrong.
This patch adds a new predicate
