https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67174
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #5 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to paul.richard.tho...@gmail.com from comment #4)
> reworked to use the gcc error reporting mechanisms. There is now a
> flag, which determines whether or not the line where the error occurs
> is displayed or not. I suspect that something is causing this flag to
https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#Diagnostic-Message-Formatting-Options
The flag is -fdiagnostics-show-caret. The testsuite uses
-fno-diagnostics-show-caret, since we actually cannot test the caret line (the
source line with the '(1)' or '(2)' or '^' symbol below) and the info given by
-fno-diagnostics-show-caret is enough to test precise locations. The Fortran FE
testsuite uses several complicated regex to remove all possible forms of the
caret line and keep only the location information and the diagnostic text, but
I think this should not be necessary anymore since everything was converted to
the common machinery and the output with -fno-diagnostics-show-caret is already
in the desired form for the testsuite.
