https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78351
--- Comment #12 from Dr. Kevin B. Beard <kevin.b.beard at nasa dot gov> ---
Hi,
Generally our (NASA's) legacy FORTRAN's READ's use no special flags
(IOSTAT=, ERR=, END=, etc.).
We have a huge amount of code going back to the early 1960's; some is an
eclectic mixture
of FORTRAN IV, 66, 77, and 90.
I have always been told (and seen) that since 77 a comma terminates a
field properly - I
don't have a copy of the actual standards documents
(https://docs.oracle.com/cd/E19957-01/805-4939/z4000743a36d/index.html)
I try to avoid FMT=* because it often gives problems when different
compilers are used.
Thanks,
Kevin
----------------------------------------------------------
Dr. Kevin B. Beard, Lockheed Martin Corporation
kevin.b.be...@nasa.gov
281-244-8534
room 548C, building 45, NASA Johnson Space Center
US Mail: Kevin B. Beard, bldg 45, mail code Wyle/OPS/45, P.O.Box 58487,
Houston, TX 77258
________________________________________
From: jvdelisle at gcc dot gnu.org [gcc-bugzi...@gcc.gnu.org]
Sent: Tuesday, November 15, 2016 6:36 PM
To: Beard, Kevin B. (JSC-SD2)[WYLE LABORATORIES, INC.]
Subject: [Bug fortran/78351] comma not terminating READ of formatted input
field - ok in 4.1.7, not 4.4.7- maybe related to 25419?
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?
--
You are receiving this mail because:
You are on the CC list for the bug.
You reported the bug.
