public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-3545] tree-optimization/107447 - avoid hoisting returns-twice calls in LIM
Date: Fri, 28 Oct 2022 13:07:25 +0000 (GMT)	[thread overview]
Message-ID: <20221028130725.F14B7382C151@sourceware.org> (raw)

https://gcc.gnu.org/g:1add3635563b39e3c0e9bed4930d11b3f605fdd3

commit r13-3545-g1add3635563b39e3c0e9bed4930d11b3f605fdd3
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Oct 28 14:20:36 2022 +0200

    tree-optimization/107447 - avoid hoisting returns-twice calls in LIM
    
    The following makes sure to not hoist returns-twice calls in LIM
    since we have no way to move the abnormal edge associated with it
    and we are prone having stray abnormal edges in the IL which will
    then cause IL verification failures even when the actual call
    does not return twice.
    
            PR tree-optimization/107447
            * tree-ssa-loop-im.cc (determine_max_movement): Do not
            hoist returns-twice calls.
    
            * gcc.dg/torture/pr107447.c: New testcase.

Diff:
---
 gcc/testsuite/gcc.dg/torture/pr107447.c | 23 +++++++++++++++++++++++
 gcc/tree-ssa-loop-im.cc                 | 13 +++++++++----
 2 files changed, 32 insertions(+), 4 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/torture/pr107447.c b/gcc/testsuite/gcc.dg/torture/pr107447.c
new file mode 100644
index 00000000000..06f7b7b15ae
--- /dev/null
+++ b/gcc/testsuite/gcc.dg/torture/pr107447.c
@@ -0,0 +1,23 @@
+/* { dg-do compile } */
+
+int n;
+
+void
+bar (int, int);
+
+__attribute__ ((noinline, returns_twice)) int
+zero (void)
+{
+  return 0;
+}
+
+void
+foo (void)
+{
+  (void) zero ();
+
+  n = 0;
+
+  for (;;)
+    bar (zero (), n);
+}
diff --git a/gcc/tree-ssa-loop-im.cc b/gcc/tree-ssa-loop-im.cc
index 2ea815050d1..2119d4072d3 100644
--- a/gcc/tree-ssa-loop-im.cc
+++ b/gcc/tree-ssa-loop-im.cc
@@ -835,10 +835,15 @@ determine_max_movement (gimple *stmt, bool must_preserve_exec)
 
       return true;
     }
-  else
-    FOR_EACH_SSA_TREE_OPERAND (val, stmt, iter, SSA_OP_USE)
-      if (!add_dependency (val, lim_data, loop, true))
-	return false;
+
+  /* A stmt that receives abnormal edges cannot be hoisted.  */
+  if (is_a <gcall *> (stmt)
+      && (gimple_call_flags (stmt) & ECF_RETURNS_TWICE))
+    return false;
+
+  FOR_EACH_SSA_TREE_OPERAND (val, stmt, iter, SSA_OP_USE)
+    if (!add_dependency (val, lim_data, loop, true))
+      return false;
 
   if (gimple_vuse (stmt))
     {

                 reply	other threads:[~2022-10-28 13:07 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=20221028130725.F14B7382C151@sourceware.org \
    --to=rguenth@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).