public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94606] [10 Regression] ICE creating fixed-length SVE predicate
Date: Thu, 16 Apr 2020 14:45:52 +0000	[thread overview]
Message-ID: <bug-94606-4-et0rPVCDq0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94606-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94606

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>:

https://gcc.gnu.org/g:26bebf576ddcdcfb596f07e8c2896f17c48516e7

commit r10-7759-g26bebf576ddcdcfb596f07e8c2896f17c48516e7
Author: Richard Sandiford <richard.sandiford@arm.com>
Date:   Wed Apr 15 13:52:20 2020 +0100

    aarch64: Fix mismatched SVE predicate modes [PR94606]

    For this testcase we ended up generating the invalid rtl:

    (insn 10 9 11 2 (set (reg:VNx16BI 105)
            (and:VNx16BI (xor:VNx16BI (reg:VNx8BI 103)
                    (reg:VNx16BI 104))
                (reg:VNx16BI 104))) "/tmp/bar.c":9:12 -1
         (nil))

    Fixed by taking the VNx16BI lowpart.  It's safe to do that here because
    the gp (r104) masks out the extra odd-indexed bits.

    2020-04-16  Richard Sandiford  <richard.sandiford@arm.com>

    gcc/
            PR target/94606
            * config/aarch64/aarch64.c (aarch64_expand_sve_const_pred_eor):
Take
            the VNx16BI lowpart of the recursively-generated constant.

    gcc/testsuite/
            PR target/94606
            * gcc.dg/vect/pr94606.c: New test.

  parent reply	other threads:[~2020-04-16 14:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15 12:38 [Bug target/94606] New: " rsandifo at gcc dot gnu.org
2020-04-15 12:39 ` [Bug target/94606] " rsandifo at gcc dot gnu.org
2020-04-15 12:58 ` rguenth at gcc dot gnu.org
2020-04-16 14:45 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-16 14:48 ` rsandifo at gcc dot gnu.org

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=bug-94606-4-et0rPVCDq0@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).