public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106510] [13 Regression] arm : ice in gimple_range_operand1, at gimple-range-fold.cc:485
Date: Tue, 02 Aug 2022 20:52:20 +0000	[thread overview]
Message-ID: <bug-106510-4-NRFNI2mxCR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106510-4@http.gcc.gnu.org/bugzilla/>

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

Aldy Hernandez <aldyh at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-08-02
             Status|UNCONFIRMED                 |NEW
                 CC|                            |amacleod at redhat dot com
     Ever confirmed|0                           |1

--- Comment #5 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
BTW, (In reply to David Binderman from comment #1)
> Reduced C code seems to be:
> 
> void ine_ok() {
>   float y, x;
>   if (x < y || x > y || y)
>     abort();
> }
> 
> Same problem exists on native x86_64, so I will have a go at finding a git
> range.

BTW, test exhibits undefined behavior, though putting x and y as arguments also
ICEs.

GORI wants all the relational operators defined, and is asserting so.

What's missing is the LGBT operator ;-).

diff --git a/gcc/range-op-float.cc b/gcc/range-op-float.cc
index 4fbd96a7479..1725c73e39c 100644
--- a/gcc/range-op-float.cc
+++ b/gcc/range-op-float.cc
@@ -747,6 +747,7 @@ floating_op_table::floating_op_table ()
   set (UNGE_EXPR, fop_relop_unknown);
   set (UNGT_EXPR, fop_relop_unknown);
   set (UNEQ_EXPR, fop_relop_unknown);
+  set (LTGT_EXPR, fop_relop_unknown);
   set (ORDERED_EXPR, fop_ordered);
   set (UNORDERED_EXPR, fop_unordered);
 }

I won't be able to get to this today.  If someone could test and push, it'd be
great.  Otherwise, I'll get to it tomorrow.

  parent reply	other threads:[~2022-08-02 20:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 19:36 [Bug target/106510] New: " dcb314 at hotmail dot com
2022-08-02 19:44 ` [Bug tree-optimization/106510] [13 Regression] " pinskia at gcc dot gnu.org
2022-08-02 19:46 ` dcb314 at hotmail dot com
2022-08-02 19:49 ` pinskia at gcc dot gnu.org
2022-08-02 19:50 ` dcb314 at hotmail dot com
2022-08-02 19:57 ` dcb314 at hotmail dot com
2022-08-02 20:52 ` aldyh at gcc dot gnu.org [this message]
2022-08-02 23:24 ` cvs-commit at gcc dot gnu.org
2022-08-02 23:24 ` 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-106510-4-NRFNI2mxCR@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).