public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/103193] gcc for x86_64: wrong code generation: ucomiss instead of comiss
Date: Fri, 12 Nov 2021 07:35:23 +0000	[thread overview]
Message-ID: <bug-103193-4-DGhxA7vvqk@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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |x86_64-*-* i?86-*-*
          Component|target                      |middle-end
     Ever confirmed|0                           |1
                 CC|                            |rguenth at gcc dot gnu.org
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2021-11-12

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to joseph@codesourcery.com from comment #3)
> Converting from >= to == is inappropriate (because >= should raise invalid 
> for all NaN operands but == should do so only for signaling NaNs).  If 
> that's happening in architecture-independent code, then this is an 
> architecture-independent bug.

/* Simplify comparison of something with itself.  For IEEE
   floating-point, we can only do some of these simplifications.  */
(for cmp (eq ge le)
 (simplify
  (cmp @0 @0)
  (if (! FLOAT_TYPE_P (TREE_TYPE (@0))
       || ! HONOR_NANS (@0))
   { constant_boolean_node (true, type); }
   (if (cmp != EQ_EXPR)
    (eq @0 @0)))))

does this.  The folding to == happens unconditionally.  As I understand you
the condition that applies to the constant folding should apply to the
folding to EQ as well, which means we effectively need to remove the
canonicalization to EQ (since when it would be valid we can fold to constant
true)?

There are similar transforms following:

(for cmp (unle unge uneq)
 (simplify
  (cmp @0 @0)
  { constant_boolean_node (true, type); }))
(for cmp (unlt ungt)
 (simplify
  (cmp @0 @0)
  (unordered @0 @0)))
(simplify
 (ltgt @0 @0)
 (if (!flag_trapping_math)
  { constant_boolean_node (false, type); }))

  parent reply	other threads:[~2021-11-12  7:35 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
2021-11-11 21:29 ` joseph at codesourcery dot com
2021-11-12  7:35 ` rguenth at gcc dot gnu.org [this message]
2021-11-12 23:35 ` [Bug middle-end/103193] " 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-DGhxA7vvqk@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).