diff options
Diffstat (limited to 'gcc/java')
| -rw-r--r-- | gcc/java/ChangeLog | 5 | ||||
| -rw-r--r-- | gcc/java/verify-impl.c | 10 |
2 files changed, 11 insertions, 4 deletions
diff --git a/gcc/java/ChangeLog b/gcc/java/ChangeLog index 4c967594797..bfc0df12a99 100644 --- a/gcc/java/ChangeLog +++ b/gcc/java/ChangeLog @@ -1,3 +1,8 @@ +2005-06-24 Tom Tromey <tromey@redhat.com> + + * verify-impl.c (verify_instructions_0): Correctly handle + situation where PC falls off end. + 2005-06-23 Bryce McKinlay <mckinlay@redhat.com> PR java/20697 diff --git a/gcc/java/verify-impl.c b/gcc/java/verify-impl.c index db6078e9c97..f7876387481 100644 --- a/gcc/java/verify-impl.c +++ b/gcc/java/verify-impl.c @@ -2251,10 +2251,12 @@ verify_instructions_0 (void) else { /* We only have to do this checking in the situation where - control flow falls through from the previous - instruction. Otherwise merging is done at the time we - push the branch. */ - if (vfr->states[vfr->PC] != NULL) + control flow falls through from the previous instruction. + Otherwise merging is done at the time we push the branch. + Note that we'll catch the off-the-end problem just + below. */ + if (vfr->PC < vfr->current_method->code_length + && vfr->states[vfr->PC] != NULL) { /* We've already visited this instruction. So merge the states together. It is simplest, but not most |