public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/94403] Missed optimization bswap Date: Mon, 30 Mar 2020 16:55:39 +0000 [thread overview] Message-ID: <bug-94403-4-AyReNGEaj8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94403-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94403 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 48147 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48147&action=edit gcc10-pr94403.patch Untested fix for the std::byte part. Not a regression, so will have to wait for GCC11. Also, if the testcase doesn't have the assignment of the parameter into a separate local temporary (i.e. when the parameter itself is addressable), then it doesn't work either, the loads stay as MEM_REFs instead of being transformed to BIT_FIELD_REFs on the parameter.
next prev parent reply other threads:[~2020-03-30 16:55 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-30 15:40 [Bug other/94403] New: " boris_oncev at hotmail dot com 2020-03-30 15:46 ` [Bug other/94403] " boris_oncev at hotmail dot com 2020-03-30 16:40 ` [Bug tree-optimization/94403] " jakub at gcc dot gnu.org 2020-03-30 16:55 ` jakub at gcc dot gnu.org [this message] 2020-03-31 9:05 ` cvs-commit at gcc dot gnu.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-94403-4-AyReNGEaj8@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).