[Bug fortran/27436] gfortran: Abort compiling if there are insufficient data descriptors in format after reversion
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27436 Dominique d'Humieres changed: What|Removed |Added CC||gerhard.steinmetz.fortran@t ||-online.de --- Comment #5 from Dominique d'Humieres --- *** Bug 66708 has been marked as a duplicate of this bug. ***
[Bug fortran/27436] gfortran: Abort compiling if there are insufficient data descriptors in format after reversion
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27436 --- Comment #4 from Dominique d'Humieres --- See also pr28397.
[Bug fortran/27436] gfortran: Abort compiling if there are insufficient data descriptors in format after reversion
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27436 Dominique d'Humieres dominiq at lps dot ens.fr changed: What|Removed |Added Status|ASSIGNED|NEW
[Bug fortran/27436] gfortran: Abort compiling if there are insufficient data descriptors in format after reversion
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27436 --- Comment #3 from Dominique d'Humieres dominiq at lps dot ens.fr --- (In reply to comment #1) Adding to my list Do you mean that you assign this PR to you?
[Bug fortran/27436] gfortran: Abort compiling if there are insufficient data descriptors in format after reversion
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27436 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|NEW |ASSIGNED CC||jvdelisle at gcc dot ||gnu.org AssignedTo|unassigned at gcc dot |jvdelisle at gcc dot |gnu.org |gnu.org --- Comment #2 from Jerry DeLisle jvdelisle at gcc dot gnu.org 2011-01-17 20:07:10 UTC --- Adding to my list
[Bug fortran/27436] gfortran: Abort compiling if there are insufficient data descriptors in format after reversion
--- Comment #1 from fxcoudert at gcc dot gnu dot org 2006-05-05 07:10 --- (In reply to comment #0) Currently, gfortran only detects that the IO format descriptor contains insufficient data at run time. It would be great (though of low priority) if it would find them at compile time. Indeed. write(*,'(abc)') n That one we could diagnose. write(10,(i7,(' abcd')), err=10) n, n This one, however, is not expected to give a warning since an err= specifier is present. It's true we could optimize it away as a goto 10, but I think that is low priority :) -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added CC||fxcoudert at gcc dot gnu dot ||org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2006-05-05 07:10:05 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27436