https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119810
James K. Lowden <jklowden at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2025-05-16
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #4 from James K. Lowden <jklowden at gcc dot gnu.org> ---
Adding a line "foo" at the end provokes the error, too. (I'm not terribly
concerned about a DATA DIVISION that ends abruptly at EOF; I'm not 100%
convinced a separator period -- which is defined as [.][[:space:]] -- can also
be [.]<<EOF>>.)
However, the problem was real, and is really fixed by 2349230d565 on our local
parser branch. Because the -include option didn't set up the filename for
diagnostics as is done for COPY, any error in the main file began with a
spurious preamble about where it came from.
