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 target/102737] [9/10/11/12 Regression] extra mov with int->double conversion and addition (incoming arguments and return) Date: Wed, 13 Oct 2021 21:25:19 +0000 [thread overview] Message-ID: <bug-102737-4-uUZQdfd00U@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102737-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102737 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |9.5 Known to fail| |10.1.0, 9.1.0 Severity|normal |enhancement Known to work| |5.1.0, 8.1.0, 8.5.0 Summary|[x86] Failure to optimize |[9/10/11/12 Regression] |out bad register usage |extra mov with int->double |involving int->double |conversion and addition |conversion |(incoming arguments and | |return) --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- GCC 8.5.0 (and before) would do: pxor %xmm1, %xmm1 cvtsi2sd %edi, %xmm1 addsd %xmm1, %xmm0 ret So this is a regression. Even with AVX, gcc has an extra move even if inputs don't have to be tied to the output: vmovsd %xmm0, %xmm0, %xmm1 vxorps %xmm0, %xmm0, %xmm0 vcvtsi2sdl %edi, %xmm0, %xmm0 vaddsd %xmm1, %xmm0, %xmm0 ret
next prev parent reply other threads:[~2021-10-13 21:25 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-13 21:08 [Bug target/102737] New: [x86] Failure to optimize out bad register usage involving int->double conversion gabravier at gmail dot com 2021-10-13 21:25 ` pinskia at gcc dot gnu.org [this message] 2021-10-13 21:27 ` [Bug target/102737] [9/10/11/12 Regression] extra mov with int->double conversion and addition (incoming arguments and return) pinskia at gcc dot gnu.org 2022-01-19 8:55 ` rguenth at gcc dot gnu.org 2022-05-27 9:46 ` [Bug target/102737] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:46 ` jakub at gcc dot gnu.org 2023-07-07 10:41 ` [Bug target/102737] [11/12/13/14 " rguenth 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-102737-4-uUZQdfd00U@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).