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 rtl-optimization/104059] [12 Regression] cprop_hardreg propgates hard registers for mov instructions between different REG_CLASS without considering cost Date: Mon, 17 Jan 2022 04:56:12 +0000 [thread overview] Message-ID: <bug-104059-4-ltXaAsWPe6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104059-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104059 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |12.0 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2022-01-17 Summary|cprop_hardreg propgates |[12 Regression] |hard registers for mov |cprop_hardreg propgates |instructions between |hard registers for mov |different REG_CLASS without |instructions between |considering cost |different REG_CLASS without | |considering cost Component|target |rtl-optimization --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed, I see it even on aarch64: addv s0, v0.4s fmov w0, s0 fmov w1, s0 In GCC 11 we get: ldr q0, [x1] shl v0.4s, v0.4s, 1 addv s0, v0.4s fmov w0, s0 lsr w1, w0, 16 add w0, w1, w0, uxth lsr w0, w0, 1 While on the trunk we get: shl v0.4s, v0.4s, 1 addv s0, v0.4s fmov w0, s0 fmov w1, s0 and w0, w0, 65535 add w0, w0, w1, lsr 16 lsr w0, w0, 1
next prev parent reply other threads:[~2022-01-17 4:56 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-17 3:36 [Bug target/104059] New: " crazylht at gmail dot com 2022-01-17 4:56 ` pinskia at gcc dot gnu.org [this message] 2022-01-17 8:40 ` [Bug rtl-optimization/104059] [12 Regression] " rguenth at gcc dot gnu.org 2022-01-17 17:53 ` jakub at gcc dot gnu.org 2022-01-17 17:59 ` pinskia at gcc dot gnu.org 2022-01-19 3:35 ` pinskia at gcc dot gnu.org 2022-01-19 3:41 ` pinskia at gcc dot gnu.org 2022-01-27 6:02 ` crazylht at gmail dot com 2022-02-08 4:39 ` cvs-commit at gcc dot gnu.org 2022-02-15 6:37 ` crazylht at gmail dot com
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-104059-4-ltXaAsWPe6@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).