public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Macleod <amacleod@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-3031] Don't process undefined range.
Date: Mon,  3 Oct 2022 14:14:10 +0000 (GMT)	[thread overview]
Message-ID: <20221003141410.729B33858D38@sourceware.org> (raw)

https://gcc.gnu.org/g:f41d1b39a6443fad38c36af34b1baa384954ca80

commit r13-3031-gf41d1b39a6443fad38c36af34b1baa384954ca80
Author: Andrew MacLeod <amacleod@redhat.com>
Date:   Sun Oct 2 18:43:35 2022 -0400

    Don't process undefined range.
    
    No need to continue processing an undefined range.
    
            gcc/
            PR tree-optimization/107109
            * range-op.cc (adjust_op1_for_overflow): Don't process undefined.
            gcc/testsuite/
            * gcc.dg/pr107109.c: New.

Diff:
---
 gcc/range-op.cc                 |  2 ++
 gcc/testsuite/gcc.dg/pr107109.c | 21 +++++++++++++++++++++
 2 files changed, 23 insertions(+)

diff --git a/gcc/range-op.cc b/gcc/range-op.cc
index 7ef980315b6..4f647abd91c 100644
--- a/gcc/range-op.cc
+++ b/gcc/range-op.cc
@@ -1370,6 +1370,8 @@ static void
 adjust_op1_for_overflow (irange &r, const irange &op2, relation_kind rel,
 			 bool add_p)
 {
+  if (r.undefined_p ())
+    return;
   tree type = r.type ();
   // Check for unsigned overflow and calculate the overflow part.
   signop s = TYPE_SIGN (type);
diff --git a/gcc/testsuite/gcc.dg/pr107109.c b/gcc/testsuite/gcc.dg/pr107109.c
new file mode 100644
index 00000000000..e3036f6ff22
--- /dev/null
+++ b/gcc/testsuite/gcc.dg/pr107109.c
@@ -0,0 +1,21 @@
+/* { dg-do compile } */
+/* { dg-options "-O1" } */
+
+int printf(const char *, ...);
+int a, b;
+void c() {
+  int d, e;
+ L:
+  a = (b && a) ^ 2756578370;
+  d = ~a + (e ^ d) ^ 2756578370;
+  if (!d)
+    printf("%d", a);
+  d = a / e;
+  goto L;
+}
+int main() {
+  if (a)
+    c();
+  return 0;
+}
+

                 reply	other threads:[~2022-10-03 14:14 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=20221003141410.729B33858D38@sourceware.org \
    --to=amacleod@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).