public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gabravier at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102224] Incorrect compile on `x * copysign(1.0, x)`
Date: Tue, 07 Sep 2021 03:01:54 +0000	[thread overview]
Message-ID: <bug-102224-4-bCz0OlZKvr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102224-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102224

--- Comment #3 from Gabriel Ravier <gabravier at gmail dot com> ---
Also seems like this might be unique to x86 as this compiles fine on Aarch64
(though while it doesn't try to do anything stupid like xoring the result with
itself, it does still not optimize the XOR_SIGN to an ABS_EXPR at the GIMPLE
level).

  parent reply	other threads:[~2021-09-07  3:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07  2:56 [Bug tree-optimization/102224] New: " gabravier at gmail dot com
2021-09-07  2:58 ` [Bug tree-optimization/102224] " gabravier at gmail dot com
2021-09-07  2:59 ` gabravier at gmail dot com
2021-09-07  3:01 ` gabravier at gmail dot com [this message]
2021-09-07  3:04 ` [Bug target/102224] " pinskia at gcc dot gnu.org
2021-09-07  3:06 ` [Bug target/102224] [12 regession] wrong code for " pinskia at gcc dot gnu.org
2021-09-07  3:07 ` gabravier at gmail dot com
2021-09-07  3:18 ` [Bug target/102224] [9/10/11/12 " gabravier at gmail dot com
2021-09-07  3:25 ` gabravier at gmail dot com
2021-09-07  6:37 ` rguenth at gcc dot gnu.org
2021-09-07  9:33 ` [Bug target/102224] [9/10/11/12 regession] wrong code for `x * copysign(1.0, x)` since r9-5298-g33142cf9cf82aa1f marxin at gcc dot gnu.org
2021-09-07  9:51 ` jakub at gcc dot gnu.org
2021-09-07 11:25 ` jakub at gcc dot gnu.org
2021-09-07 18:53 ` pinskia at gcc dot gnu.org
2021-09-08  9:26 ` cvs-commit at gcc dot gnu.org
2021-09-08 10:08 ` [Bug target/102224] [9/10/11 " jakub at gcc dot gnu.org
2021-09-08 18:02 ` cvs-commit at gcc dot gnu.org
2021-09-08 18:03 ` [Bug target/102224] [9/10 " jakub at gcc dot gnu.org
2022-05-10  8:20 ` cvs-commit at gcc dot gnu.org
2022-05-11  6:22 ` cvs-commit at gcc dot gnu.org
2022-05-11  6:36 ` jakub 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-102224-4-bCz0OlZKvr@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: link
Be 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).