public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joelh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99102] [11 Regression] SVE: Wrong code with -O2 -ftree-vectorize -march=armv8.2-a+sve -msve-vector-bits=256
Date: Thu, 25 Feb 2021 16:43:41 +0000	[thread overview]
Message-ID: <bug-99102-4-B1L1F8EsQQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99102-4@http.gcc.gnu.org/bugzilla/>

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

Joel Hutton <joelh at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2021-02-25

--- Comment #2 from Joel Hutton <joelh at gcc dot gnu.org> ---
Bisect shows

46c705e70e078f6a1920d92e49042125d5e18495 is the first bad commit
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.



is the offending commit.

  parent reply	other threads:[~2021-02-25 16:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 10:19 [Bug target/99102] New: " acoplan at gcc dot gnu.org
2021-02-15 10:49 ` [Bug target/99102] [11 Regression] " acoplan at gcc dot gnu.org
2021-02-15 12:08 ` ktkachov at gcc dot gnu.org
2021-02-25 16:43 ` joelh at gcc dot gnu.org [this message]
2021-03-03 12:22 ` joelh at gcc dot gnu.org
2021-03-05 16:18 ` joelh at gcc dot gnu.org
2021-03-10 12:26 ` cvs-commit at gcc dot gnu.org
2021-03-10 12:48 ` joelh at gcc dot gnu.org
2021-03-30 16:05 ` 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-99102-4-B1L1F8EsQQ@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).