[Bug fortran/69964] ICE on misspelled end block data, in gfc_ascii_statement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69964 --- Comment #5 from Dominique d'Humieres --- > > This appears to be fixed on trunk. > > Confirmed. I get an ICE with revision r238821, but not with r238824. > Likely fall out of r238822 (pr71883). For the record, it is also fixed on the gcc-5 and 6 branches.
[Bug fortran/69964] ICE on misspelled end block data, in gfc_ascii_statement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69964 Dominique d'Humieres changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Dominique d'Humieres --- > This appears to be fixed on trunk. Confirmed. I get an ICE with revision r238821, but not with r238824. Likely fall out of r238822 (pr71883).
[Bug fortran/69964] ICE on misspelled end block data, in gfc_ascii_statement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69964 --- Comment #3 from kargl at gcc dot gnu.org --- This appears to be fixed on trunk.
[Bug fortran/69964] ICE on misspelled end block data, in gfc_ascii_statement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69964 --- Comment #2 from kargl at gcc dot gnu.org --- Index: parse.c === --- parse.c (revision 237945) +++ parse.c (working copy) @@ -5626,8 +5628,11 @@ parse_block_data (void) while (st != ST_END_BLOCK_DATA) { - gfc_error ("Unexpected %s statement in BLOCK DATA at %C", -gfc_ascii_statement (st)); + if (st != ST_NONE) + gfc_error ("Unexpected %s statement in BLOCK DATA at %C", + gfc_ascii_statement (st)); + else + break; reject_statement (); st = next_statement (); }
[Bug fortran/69964] ICE on misspelled end block data, in gfc_ascii_statement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69964 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed||2016-02-26 Ever confirmed|0 |1 --- Comment #1 from Dominique d'Humieres --- Confirmed from 4.8 up to trunk (6.0).