https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78351
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org --- Comment #9 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- Two things going on here. First, Looking at read_decimal in read.c way back on the 4.1 branch, we did nothing special other than generate an error and return. Same code we have now. So we never tried to interpret the comma uniquely. We are getting a segfault right after the error and the backtrace is landing in the middle of read_block_direct, so the error recovery is broken. Segfault is never acceptable so I will fix that first. (error recovery) By any chance do your data streams have the data padded with spaces such that they do not violate the format width specifier? Do your actual read statements also have the END= or EOR= specifiers?