diff options
| author | rth <rth@138bc75d-0d04-0410-961f-82ee72b054a4> | 2009-09-29 23:46:02 +0000 |
|---|---|---|
| committer | rth <rth@138bc75d-0d04-0410-961f-82ee72b054a4> | 2009-09-29 23:46:02 +0000 |
| commit | e9d5f86f47e11658e51f16ff38fd87729cbe688d (patch) | |
| tree | bb03d51f9447daacfa275ffb3949c7371d4bcca9 /gcc/tree-eh.c | |
| parent | 450040e53814cea9ef1c39e5e907e08623c5594f (diff) | |
| download | gcc-e9d5f86f47e11658e51f16ff38fd87729cbe688d.tar.gz | |
* tree-eh.c (unsplit_eh): Do not unsplit if there's already
an edge to the new destination block.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@152310 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/tree-eh.c')
| -rw-r--r-- | gcc/tree-eh.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/gcc/tree-eh.c b/gcc/tree-eh.c index 0f5931e0b75..3ed92a59bc7 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, |