aboutsummaryrefslogtreecommitdiff
path: root/gcc/tree-eh.c
diff options
context:
space:
mode:
authorRichard Henderson <rth@redhat.com>2009-09-29 16:46:02 -0700
committerRichard Henderson <rth@gcc.gnu.org>2009-09-29 16:46:02 -0700
commitf8fd49b54950059ad08d6a8cc291ec07fed15108 (patch)
treebb03d51f9447daacfa275ffb3949c7371d4bcca9 /gcc/tree-eh.c
parent062a5fd1c0c9e72663e792a0e8f4066ef0f074fb (diff)
downloadgcc-f8fd49b54950059ad08d6a8cc291ec07fed15108.zip
gcc-f8fd49b54950059ad08d6a8cc291ec07fed15108.tar.gz
gcc-f8fd49b54950059ad08d6a8cc291ec07fed15108.tar.bz2
tree-eh.c (unsplit_eh): Do not unsplit if there's already an edge to the new destination block.
* tree-eh.c (unsplit_eh): Do not unsplit if there's already an edge to the new destination block. From-SVN: r152310
Diffstat (limited to 'gcc/tree-eh.c')
-rw-r--r--gcc/tree-eh.c6
1 files changed, 6 insertions, 0 deletions
diff --git a/gcc/tree-eh.c b/gcc/tree-eh.c
index 0f5931e..3ed92a5 100644
--- a/gcc/tree-eh.c
+++ b/gcc/tree-eh.c
@@ -3369,6 +3369,12 @@ unsplit_eh (eh_landing_pad lp)
return false;
}
+ /* The new destination block must not already be a destination of
+ the source block, lest we merge fallthru and eh edges and get
+ all sorts of confused. */
+ if (find_edge (e_in->src, e_out->dest))
+ return false;
+
/* ??? I can't imagine there would be PHI nodes, since by nature
of critical edge splitting this block should never have been
a dominance frontier. If cfg cleanups somehow confuse this,