public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/114319] htobe64-like function is not optimized on 32-bit x86 Date: Tue, 12 Mar 2024 18:04:06 +0000 [thread overview] Message-ID: <bug-114319-4-BxCzHSMzo2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114319-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114319 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2024-03-12 Target|x86 |ILP32 Blocks| |94094 Ever confirmed|0 |1 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed. I see the trunk even without -mno-sse does not produce the 2 bswaps. Looks like the store-merging pass is not recognizing bswap<<32 for some reason. Also I thought there was a dup somewhere ... Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94094 [Bug 94094] [meta-bug] store-merging and/or bswap load/store-merging missed optimizations
next prev parent reply other threads:[~2024-03-12 18:04 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-12 17:45 [Bug target/114319] New: " pali at kernel dot org 2024-03-12 17:49 ` [Bug middle-end/114319] " pinskia at gcc dot gnu.org 2024-03-12 17:56 ` pinskia at gcc dot gnu.org 2024-03-12 18:04 ` pinskia at gcc dot gnu.org [this message] 2024-03-12 18:07 ` pali at kernel dot org 2024-03-12 18:10 ` pinskia at gcc dot gnu.org 2024-03-13 9:47 ` rguenth at gcc dot gnu.org 2024-03-13 14:35 ` cvs-commit at gcc dot gnu.org 2024-03-13 14:38 ` jakub at gcc dot gnu.org 2024-03-13 21:31 ` pali at kernel 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-114319-4-BxCzHSMzo2@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).