http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59700
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Keywords| |diagnostic
Last reconfirmed| |2014-01-06
CC| |burnus at gcc dot gnu.org
Ever confirmed|0 |1
Summary|Misleading/buggy runtime |[4.8/4.9 Regression]
|error message: Bad integer |Misleading/buggy runtime
|for item 0 in list input |error message: Bad integer
| |for item 0 in list input
Known to fail| |4.8.2, 4.9.0
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
r203000 (2013-09-27) gives
At line 7 of file pr59700.f90
Fortran runtime error: Bad integer for item 4 in list input
while r203129 (2013-10-02) gives 'item 0'. It is likely r203086 for trunk and
r203201 for 4.8.2.
I think this due to
+
+ free_line (dtp);
snprintf (message, MSGLEN, "Bad integer for item %d in list input",
dtp->u.p.item_count);
I suspect that
+
+ free_line (dtp);
snprintf (message, MSGLEN, "Bad floating point number for item %d",
dtp->u.p.item_count);
will cause the same problem for bad floating point numbers.
