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 middle-end/111701] New: [11/12/13/14 Regression] wrong code for __builtin_signbit(x*x) Date: Thu, 05 Oct 2023 08:12:55 +0000 [thread overview] Message-ID: <bug-111701-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111701 Bug ID: 111701 Summary: [11/12/13/14 Regression] wrong code for __builtin_signbit(x*x) Product: gcc Version: 13.2.1 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: amonakov at gcc dot gnu.org CC: amonakov at gcc dot gnu.org, eggert at cs dot ucla.edu, rguenth at gcc dot gnu.org, unassigned at gcc dot gnu.org Depends on: 111655 Target Milestone: --- Target: x86_64-linux-gnu +++ This bug was initially created as a clone of Bug #111655 +++ See bug 111655 comment 11: we incorrectly deduce nonnegative_p for floating-point 'x * x', and the following aborts: __attribute__((noipa)) static int f(float *x) { *x *= *x; return __builtin_signbit(*x); } int main() { float x = -__builtin_nan(""); int s = f(&x); if (s != __builtin_signbit(x)) __builtin_abort(); } Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111655 [Bug 111655] [11/12/13/14 Regression] wrong code generated for __builtin_signbit and 0./0. on x86-64 -O2
next reply other threads:[~2023-10-05 8:12 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-05 8:12 amonakov at gcc dot gnu.org [this message] 2023-10-06 7:47 ` [Bug middle-end/111701] " rguenth at gcc dot gnu.org 2024-04-26 8:31 ` roger at nextmovesoftware 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-111701-4@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).