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/40210] gcc byte swap builtins inadequately optimized Date: Sat, 10 Jul 2021 08:34:05 +0000 [thread overview] Message-ID: <bug-40210-4-y0lgMUPbwT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-40210-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40210 Roger Sayle <roger at nextmovesoftware dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roger at nextmovesoftware dot com Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Target Milestone|--- |12.0 --- Comment #13 from Roger Sayle <roger at nextmovesoftware dot com> --- All of the (bswap-related) optimizations mentioned in PR tree-optimization/40210 are now implemented in mainline GCC.
next prev parent reply other threads:[~2021-07-10 8:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-40210-4@http.gcc.gnu.org/bugzilla/> 2011-10-07 18:23 ` pluto at agmk dot net 2011-10-07 18:29 ` pinskia at gcc dot gnu.org 2011-10-07 18:46 ` pluto at agmk dot net 2021-07-08 10:48 ` cvs-commit at gcc dot gnu.org 2021-07-10 8:34 ` roger at nextmovesoftware dot com [this message] 2009-05-20 18:48 [Bug tree-optimization/40210] New: gcc needs byte swap builtins eric-bugs at omnifarious dot org 2009-05-20 19:39 ` [Bug tree-optimization/40210] gcc byte swap builtins inadequately optimized eric-bugs at omnifarious dot org 2009-05-20 20:05 ` jakub at gcc dot gnu dot org 2009-05-20 20:22 ` eric-bugs at omnifarious dot org 2009-06-10 17:37 ` hp at gcc dot gnu dot 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-40210-4-y0lgMUPbwT@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).