This is the mail archive of the
mailing list for the GCC project.
Re: [tree-ssa] Gimplifying Java
- From: Jeff Sturm <jsturm at one-point dot com>
- To: Andrew MacLeod <amacleod at redhat dot com>
- Cc: Jeff Law <law at redhat dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 12 Jun 2003 17:14:04 -0400 (EDT)
- Subject: Re: [tree-ssa] Gimplifying Java
On 12 Jun 2003, Andrew MacLeod wrote:
> So BB5 has 12 as a successor, but there is no edge? Or you mean there
> is an edge, but nowhere to insert the code?
BB5 should _not_ have 12 as a successor, it can't get there. So, there's
nowhere to insert the code, right?
# BLOCK 5 (NameFinder.java:6). PRED: 3. SUCC: 12 6.
# BLOCK 6 (NameFinder.java:18). PRED: 5. SUCC: 8 7.
if (file.8 == 0B)
# BLOCK 7 (NameFinder.java:18). PRED: 6. SUCC: -2 10.
# BLOCK 8 (NameFinder.java:18). PRED: 6. SUCC: 9 10.
T.11 = substring.10 (file.8, T.9);
# BLOCK 9 (NameFinder.java:18). PRED: 8. SUCC: 12 10.
T.14 = parseInt.13 (T.12)
# BLOCK 10 (NameFinder.java:18). PRED: 9 8 7. SUCC: 12 11.
catch (struct java.lang.NumberFormatException)
# BLOCK 11 (NameFinder.java:18). PRED: 10. SUCC: 12.
T.15 = <<<exception object>>> - 4;
nfe = *T.15
> The edge inserter has not
> had to deal with TRY's yet, so it may not understand where to insert the
Oh, OK. That may be part of the problem indeed. It seemed to fail on the
> I'd actually like to see this whole section, including the PHI
> nodes and CFG info... It might be an easy fix inside the edge
What's the best way to include PHI nodes in the tree dump?