public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113542] [14 Regression] gcc.target/arm/bics_3.c regression after change for pr111267
Date: Fri, 08 Mar 2024 17:15:49 +0000	[thread overview]
Message-ID: <bug-113542-4-Jrxg4f8nql@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113542-4@http.gcc.gnu.org/bugzilla/>

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

Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #6 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Change the test slightly to avoid the insn matching issues.  This does leave
open the question of how best to optimize the slightly simpler sequences, where
we could do even better than we do now, but that's an enhancement and not
appropriate for gcc-14.

      parent reply	other threads:[~2024-03-08 17:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 15:46 [Bug rtl-optimization/113542] New: " roger at nextmovesoftware dot com
2024-01-24 12:48 ` [Bug rtl-optimization/113542] " rearnsha at gcc dot gnu.org
2024-01-24 16:42 ` [Bug target/113542] [14 Regression] " rearnsha at gcc dot gnu.org
2024-01-25  9:51 ` mkuvyrkov at gcc dot gnu.org
2024-01-31 14:33 ` rguenth at gcc dot gnu.org
2024-02-21 12:47 ` mkuvyrkov at gcc dot gnu.org
2024-03-07 20:47 ` law at gcc dot gnu.org
2024-03-08 17:08 ` cvs-commit at gcc dot gnu.org
2024-03-08 17:15 ` rearnsha at gcc dot gnu.org [this message]

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-113542-4-Jrxg4f8nql@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).