http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53993
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-07-18
09:28:51 UTC ---
Unfortunately, my attempts to generate a working patch failed, cf.
http://gcc.gnu.org/ml/fortran/2012-07/msg00082.html
http://gcc.gnu.org/ml/fortran/2012-07/msg00085.html
I always end up with warnings of the form "filename left but not entered".
This warning is generated in scanner.c's preprocessor_line.
I think someone needs to understand what input can be expected. In particular:
How to handle the first few lines of the CPP output, of which only the last
seems to be relevant vs. those of #line directives, all of which have no flag.
For the last failing test case, the file (gfortran -E) starts with:
# 1 "libgfortran/generated/_abs_c4.F90"
# 1 "<command-line>"
# 1 "gcc-build/x86_64-unknown-linux-gnu/libgfortran//"
# 1 "libgfortran/generated/_abs_c4.F90"
Which is one line more than before.
