public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112103] [14 regression] gcc.target/powerpc/rlwinm-0.c fails after r14-4941-gd1bb9569d70304
Date: Tue, 20 Feb 2024 19:52:28 +0000 [thread overview]
Message-ID: <bug-112103-4-gBvpug2Fbs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112103-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112103
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=114004
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #9 from Peter Bergner <bergner at gcc dot gnu.org> ---
Fixed.
(In reply to Peter Bergner from comment #5)
> We still want to remove the superfluous instruction, but that should be
> covered in a separate bug.
The fixing of the superfluous insn is being tracked in PR114004.
prev parent reply other threads:[~2024-02-20 19:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 16:44 [Bug target/112103] New: " seurer at gcc dot gnu.org
2023-10-26 21:34 ` [Bug target/112103] " roger at nextmovesoftware dot com
2023-10-27 13:03 ` rguenth at gcc dot gnu.org
2023-11-09 18:35 ` segher at gcc dot gnu.org
2023-11-09 18:37 ` segher at gcc dot gnu.org
2024-01-15 13:57 ` rguenth at gcc dot gnu.org
2024-01-19 16:48 ` bergner at gcc dot gnu.org
2024-02-16 19:01 ` jakub at gcc dot gnu.org
2024-02-19 21:42 ` bergner at gcc dot gnu.org
2024-02-19 22:24 ` bergner at gcc dot gnu.org
2024-02-19 22:40 ` bergner at gcc dot gnu.org
2024-02-20 19:45 ` cvs-commit at gcc dot gnu.org
2024-02-20 19:52 ` bergner 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-112103-4-gBvpug2Fbs@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).