public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/114522] New: [14 regression] gcc.target/arm/aes_xor_combine.c scan-assembler-not veor fails after r14-9692-g839bc42772ba7a
Date: Thu, 28 Mar 2024 17:09:53 +0000	[thread overview]
Message-ID: <bug-114522-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 114522
           Summary: [14 regression] gcc.target/arm/aes_xor_combine.c
                    scan-assembler-not veor fails after
                    r14-9692-g839bc42772ba7a
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: clyon at gcc dot gnu.org
                CC: segher at gcc dot gnu.org
  Target Milestone: ---

After g:839bc42772ba7af66af3bd16efed4a69511312ae, r14-9692-g839bc42772ba7a we
have noticed a regression on arm:
FAIL: gcc.target/arm/aes_xor_combine.c scan-assembler-not veor

commit 839bc42772ba7af66af3bd16efed4a69511312ae (HEAD)
Author: Segher Boessenkool <segher@kernel.crashing.org>
Date:   Wed Mar 27 14:09:52 2024 +0000

    combine: Don't combine if I2 does not change

This might be the same problem as other PRs reported after this commit.

             reply	other threads:[~2024-03-28 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 17:09 clyon at gcc dot gnu.org [this message]
2024-03-28 17:25 ` [Bug rtl-optimization/114522] " pinskia at gcc dot gnu.org
2024-03-29 23:46 ` law at gcc dot gnu.org
2024-04-02  8:24 ` rguenth at gcc dot gnu.org
2024-04-10  6:00 ` [Bug rtl-optimization/114522] [15 " rguenth at gcc dot gnu.org
2024-05-27 10:11 ` clyon 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-114522-4@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).