public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96582] aarch64:ICE during GIMPLE pass: veclower
Date: Thu, 25 Mar 2021 15:10:58 +0000	[thread overview]
Message-ID: <bug-96582-4-gVNc69We4i@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96582-4@http.gcc.gnu.org/bugzilla/>

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

Alex Coplan <acoplan at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |acoplan at gcc dot gnu.org

--- Comment #5 from Alex Coplan <acoplan at gcc dot gnu.org> ---
FWIW, the ICE was "fixed" with
r11-4912-g46c705e70e078f6a1920d92e49042125d5e18495:

commit 46c705e70e078f6a1920d92e49042125d5e18495
Author: Richard Sandiford <richard.sandiford@arm.com>
Date:   Wed Nov 11 11:42:46 2020 +0000

    aarch64: Support SVE comparisons for unpacked integers

    This patch adds support for comparing unpacked SVE integer vectors,
    such as byte elements stored in the bottom bytes of halfword
    containers.  It also adds support for selects between unpacked
    SVE vectors (both integer and floating-point), since selects and
    compares are closely tied via the vcond optab interface.

so not sure if the issue was really fixed or perhaps just hidden.

  parent reply	other threads:[~2021-03-25 15:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12  7:06 [Bug target/96582] New: " z.zhanghaijian at huawei dot com
2020-08-12 13:45 ` [Bug target/96582] " rsandifo at gcc dot gnu.org
2020-08-12 13:46 ` rsandifo at gcc dot gnu.org
2021-03-25  9:04 ` ktkachov at gcc dot gnu.org
2021-03-25  9:36 ` rguenth at gcc dot gnu.org
2021-03-25 15:10 ` acoplan at gcc dot gnu.org [this message]
2021-03-26 17:58 ` 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-96582-4-gVNc69We4i@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).