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 tree-optimization/99520] Failure to detect bswap pattern Date: Thu, 25 Nov 2021 20:28:23 +0000 [thread overview] Message-ID: <bug-99520-4-bK60WDT3J4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99520-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99520 Roger Sayle <roger at nextmovesoftware dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |12.0 CC| |roger at nextmovesoftware dot com Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from Roger Sayle <roger at nextmovesoftware dot com> --- This PR is now fixed on mainline. Thanks to Jakub (my apologies if I'd seen comment #2 I wouldn't of accidentally broken things; aka PR tree-optimization/103376, fortunately Jakub was able to quickly correct my oversight).
prev parent reply other threads:[~2021-11-25 20:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-10 15:54 [Bug middle-end/99520] New: " ktkachov at gcc dot gnu.org 2021-03-10 16:03 ` [Bug middle-end/99520] " jakub at gcc dot gnu.org 2021-03-10 16:13 ` jakub at gcc dot gnu.org 2021-03-10 16:17 ` jakub at gcc dot gnu.org 2021-03-10 16:19 ` ktkachov at gcc dot gnu.org 2021-03-10 16:28 ` jakub at gcc dot gnu.org 2021-03-10 17:43 ` ktkachov at gcc dot gnu.org 2021-03-11 8:10 ` [Bug tree-optimization/99520] " rguenth at gcc dot gnu.org 2021-11-21 14:46 ` pinskia at gcc dot gnu.org 2021-11-25 20:28 ` roger at nextmovesoftware dot com [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-99520-4-bK60WDT3J4@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: linkBe 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).