public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
To: Christophe Lyon <Christophe.Lyon@arm.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH] arm: Restrict support of vectors of boolean immediates (PR target/104662)
Date: Wed, 4 May 2022 08:03:13 +0000	[thread overview]
Message-ID: <PAXPR08MB6926C2EA1584DCCB885598BB93C39@PAXPR08MB6926.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <1cf75731-672e-b16b-02af-5ea386aa7545@arm.com>



> -----Original Message-----
> From: Gcc-patches <gcc-patches-
> bounces+kyrylo.tkachov=arm.com@gcc.gnu.org> On Behalf Of Christophe
> Lyon via Gcc-patches
> Sent: Wednesday, May 4, 2022 8:51 AM
> To: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] arm: Restrict support of vectors of boolean immediates
> (PR target/104662)
> 
> ping?
> 
> On 4/20/22 10:50, Christophe Lyon wrote:
> > This simple patch avoids the ICE described in the PR:
> > internal compiler error: in simd_valid_immediate, at
> config/arm/arm.cc:12866
> >
> > with an early exit from simd_valid_immediate if we are trying to
> > handle a vector of booleans and MVE is not enabled.
> >
> > We still get an ICE when compiling the existing
> > gcc.dg/rtl/arm/mve-vxbi.c without -march=armv8.1-m.main+mve:
> >
> > error: unrecognizable insn:
> > (insn 7 5 8 2 (set (reg:V4BI 114)
> >          (const_vector:V4BI [
> >                  (const_int 1 [0x1])
> >                  (const_int 0 [0]) repeated x2
> >                  (const_int 1 [0x1])
> >              ])) -1
> >       (nil))
> > during RTL pass: ira
> >
> > but there's little we can do since the testcase explicitly creates
> > vectors of booleans which do need MVE.
> >
> > That is the reason why I do not add a testcase.

Ok if testing is fine.
Thanks,
Kyrill

> >
> > 2022-04-19  Christophe Lyon  <christophe.lyon@arm.com>
> >
> > 	PR target/104662
> > 	* config/arm/arm.cc (simd_valid_immediate): Exit when input is a
> > 	vector of booleans and MVE is not enabled.
> > ---
> >   gcc/config/arm/arm.cc | 3 +++
> >   1 file changed, 3 insertions(+)
> >
> > diff --git a/gcc/config/arm/arm.cc b/gcc/config/arm/arm.cc
> > index 14e2fdfeafa..69a18c2f157 100644
> > --- a/gcc/config/arm/arm.cc
> > +++ b/gcc/config/arm/arm.cc
> > @@ -12849,6 +12849,9 @@ simd_valid_immediate (rtx op, machine_mode
> mode, int inverse,
> >   	  || n_elts * innersize != 16))
> >       return -1;
> >
> > +  if (!TARGET_HAVE_MVE && GET_MODE_CLASS (mode) ==
> MODE_VECTOR_BOOL)
> > +    return -1;
> > +
> >     /* Vectors of float constants.  */
> >     if (GET_MODE_CLASS (mode) == MODE_VECTOR_FLOAT)
> >       {

  reply	other threads:[~2022-05-04  8:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  8:50 Christophe Lyon
2022-05-04  7:50 ` Christophe Lyon
2022-05-04  8:03   ` Kyrylo Tkachov [this message]
2022-05-04  8:22     ` Christophe Lyon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PAXPR08MB6926C2EA1584DCCB885598BB93C39@PAXPR08MB6926.eurprd08.prod.outlook.com \
    --to=kyrylo.tkachov@arm.com \
    --cc=Christophe.Lyon@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).