public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/89310] Poor code generation returning float field from a struct Date: Wed, 24 Jun 2020 18:12:20 +0000 [thread overview] Message-ID: <bug-89310-4-Y0cTMiXkn8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89310-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89310 --- Comment #4 from Segher Boessenkool <segher at gcc dot gnu.org> --- Maybe you can make a define_insn_and_split for the lshrdi3 plus this? Which will split to an insn fewer immediately. If you split after reload you need many extra patterns to get the most basic optimisations done for its result... But (at least in this case) you do not need a peephole at least ;-)
next prev parent reply other threads:[~2020-06-24 18:12 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89310-4@http.gcc.gnu.org/bugzilla/> 2020-06-23 1:29 ` luoxhu at gcc dot gnu.org 2020-06-24 18:12 ` segher at gcc dot gnu.org [this message] 2020-06-28 9:56 ` luoxhu at gcc dot gnu.org 2020-06-29 17:46 ` segher at gcc dot gnu.org 2020-07-02 23:12 ` segher at gcc dot gnu.org 2020-07-21 3:37 ` cvs-commit at gcc dot gnu.org 2020-07-22 1:34 ` luoxhu 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-89310-4-Y0cTMiXkn8@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).