public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-4131] [PR tree-optimization/107732] [range-ops] Handle attempt to abs() negatives.
Date: Thu, 17 Nov 2022 17:43:23 +0000 (GMT)	[thread overview]
Message-ID: <20221117174323.B18E73853D55@sourceware.org> (raw)

https://gcc.gnu.org/g:4e306222f442f8d4c6fc6da997ab756a5e43e36e

commit r13-4131-g4e306222f442f8d4c6fc6da997ab756a5e43e36e
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Thu Nov 17 16:47:17 2022 +0100

    [PR tree-optimization/107732] [range-ops] Handle attempt to abs() negatives.
    
    The threader is creating a scenario where we are trying to solve:
    
            [NEGATIVES] = abs(x)
    
    While solving this we have an intermediate value of UNDEFINED because
    we have no positive numbers.  But then we try to union the negative
    pair to the final result by querying the bounds.  Since neither
    UNDEFINED nor NAN have bounds, they need to be specially handled.
    
            PR tree-optimization/107732
    
    gcc/ChangeLog:
    
            * range-op-float.cc (foperator_abs::op1_range): Early exit when
            result is undefined.
    
    gcc/testsuite/ChangeLog:
    
            * gcc.dg/tree-ssa/pr107732.c: New test.

Diff:
---
 gcc/range-op-float.cc                    |  2 +-
 gcc/testsuite/gcc.dg/tree-ssa/pr107732.c | 13 +++++++++++++
 2 files changed, 14 insertions(+), 1 deletion(-)

diff --git a/gcc/range-op-float.cc b/gcc/range-op-float.cc
index adb0cbaa6d5..ee88511eba0 100644
--- a/gcc/range-op-float.cc
+++ b/gcc/range-op-float.cc
@@ -1407,7 +1407,7 @@ foperator_abs::op1_range (frange &r, tree type,
       neg_nan.set_nan (type, true);
       r.union_ (neg_nan);
     }
-  if (r.known_isnan ())
+  if (r.known_isnan () || r.undefined_p ())
     return true;
   // Then add the negative of each pair:
   // ABS(op1) = [5,20] would yield op1 => [-20,-5][5,20].
diff --git a/gcc/testsuite/gcc.dg/tree-ssa/pr107732.c b/gcc/testsuite/gcc.dg/tree-ssa/pr107732.c
new file mode 100644
index 00000000000..b216f38db0e
--- /dev/null
+++ b/gcc/testsuite/gcc.dg/tree-ssa/pr107732.c
@@ -0,0 +1,13 @@
+// { dg-do compile }
+// { dg-options "-O2" }
+
+double sqrt(double);
+double a, b, c;
+void d() {
+  for (;;) {
+    c = __builtin_fabs(a);
+    sqrt(c);
+    if (a)
+      a = b;
+  }
+}

                 reply	other threads:[~2022-11-17 17:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221117174323.B18E73853D55@sourceware.org \
    --to=aldyh@gcc.gnu.org \
    --cc=gcc-cvs@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).