public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roger at nextmovesoftware dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105991] [12/13 Regression] rldicl+sldi+add generated instead of rldimi
Date: Fri, 24 Jun 2022 09:49:22 +0000 [thread overview]
Message-ID: <bug-105991-4-PM4U8QHRd5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105991-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105991
Roger Sayle <roger at nextmovesoftware dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|12.2 |13.0
--- Comment #7 from Roger Sayle <roger at nextmovesoftware dot com> ---
This should now be fixed on mainline. If anyone feels strongly that the fix
should be backported to the GCC 12 branch, please feel free to reopen this PR.
Thanks again to Marek.
next prev parent reply other threads:[~2022-06-24 9:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 17:09 [Bug target/105991] New: " mpolacek at gcc dot gnu.org
2022-06-15 17:10 ` [Bug target/105991] [12/13 Regression] " mpolacek at gcc dot gnu.org
2022-06-16 7:57 ` roger at nextmovesoftware dot com
2022-06-16 14:49 ` mpolacek at gcc dot gnu.org
2022-06-16 17:33 ` mpolacek at gcc dot gnu.org
2022-06-18 1:55 ` segher at gcc dot gnu.org
2022-06-18 6:30 ` roger at nextmovesoftware dot com
2022-06-21 23:10 ` cvs-commit at gcc dot gnu.org
2022-06-24 9:49 ` roger at nextmovesoftware dot com [this message]
2022-06-24 15:33 ` segher at gcc dot gnu.org
2022-07-04 13:03 ` [Bug target/105991] [12 " cvs-commit at gcc dot gnu.org
2023-04-26 6:56 ` rguenth at gcc dot gnu.org
2023-04-26 8:01 ` roger at nextmovesoftware dot com
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-105991-4-PM4U8QHRd5@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).