public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103193] gcc for x86_64: wrong code generation: ucomiss instead of comiss Date: Thu, 11 Nov 2021 20:07:41 +0000 [thread overview] Message-ID: <bug-103193-4-JyXzAOANpu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103193-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103193 --- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> --- Here is compilable testcase: _Bool a (void) { #pragma STDC FENV_ACCESS ON float f; _Bool b; f = __builtin_nan (""); b = f >= f; // ucomiss (wrong), comiss (correct) return b; } Tree optimizers (_.optimized dump) already give us: <bb 2> : f_1 = Nan; b_2 = f_1 == f_1; _3 = b_2; However, f_1 == f_1 expands with UNSPEC_NOTRAP RTX which gives us ucomiss.
next prev parent reply other threads:[~2021-11-11 20:07 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-11 15:19 [Bug c/103193] New: " pavel.morozkin at gmail dot com 2021-11-11 17:41 ` [Bug target/103193] " joseph at codesourcery dot com 2021-11-11 20:07 ` ubizjak at gmail dot com [this message] 2021-11-11 21:29 ` joseph at codesourcery dot com 2021-11-12 7:35 ` [Bug middle-end/103193] " rguenth at gcc dot gnu.org 2021-11-12 23:35 ` joseph at codesourcery dot com 2021-11-15 10:12 ` rguenth at gcc dot gnu.org 2021-11-24 10:02 ` cvs-commit at gcc dot gnu.org 2021-11-24 10:07 ` rguenth at gcc dot gnu.org 2022-07-22 11:21 ` cvs-commit at gcc dot gnu.org 2022-07-22 11:23 ` 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-103193-4-JyXzAOANpu@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).