public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111694] [13/14 Regression] Wrong behavior for signbit of negative zero when optimizing Date: Wed, 04 Oct 2023 18:31:30 +0000 [thread overview] Message-ID: <bug-111694-4-eg0V6XKKA8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111694-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111694 Alexander Monakov <amonakov at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amonakov at gcc dot gnu.org Component|web |tree-optimization Summary|Wrong behavior for signbit |[13/14 Regression] Wrong |of negative zero when |behavior for signbit of |optimizing |negative zero when | |optimizing Keywords| |wrong-code --- Comment #1 from Alexander Monakov <amonakov at gcc dot gnu.org> --- Reduced: #define signbit(x) __builtin_signbit(x) static void test(double l, double r) { if (l == r && (signbit(l) || signbit(r))) ; else __builtin_abort(); } int main() { test(0.0, -0.0); }
next prev parent reply other threads:[~2023-10-04 18:31 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-04 17:09 [Bug web/111694] New: " alonzakai at gmail dot com 2023-10-04 18:31 ` amonakov at gcc dot gnu.org [this message] 2023-10-04 19:09 ` [Bug tree-optimization/111694] [13/14 Regression] " pinskia at gcc dot gnu.org 2023-10-05 7:37 ` rguenth at gcc dot gnu.org 2023-10-06 17:30 ` amacleod at redhat dot com 2023-10-09 17:10 ` cvs-commit at gcc dot gnu.org 2023-10-09 17:11 ` amacleod at redhat dot com 2023-10-09 17:18 ` amonakov at gcc dot gnu.org 2023-10-09 17:36 ` amacleod at redhat dot com 2023-10-09 19:37 ` amacleod at redhat dot com 2023-10-11 20:45 ` cvs-commit at gcc dot gnu.org 2023-10-11 20:48 ` amacleod at redhat 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-111694-4-eg0V6XKKA8@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).