[Bug fortran/53934] Better CPP macro diagnostics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53934 Bug 53934 depends on bug 44054, which changed state. Bug 44054 Summary: Handle -Werror, -Werror=, -fdiagnostics-show-option, !GCC$ diagnostic (pragmas) and color https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44054 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED
[Bug fortran/53934] Better CPP macro diagnostics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53934 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed||2015-11-07 Ever confirmed|0 |1
[Bug fortran/53934] Better CPP macro diagnostics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53934 --- Comment #3 from Manuel López-Ibáñez manu at gcc dot gnu.org --- *** Bug 49766 has been marked as a duplicate of this bug. ***
[Bug fortran/53934] Better CPP macro diagnostics
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53934 Bug 53934 depends on bug 53552, which changed state. Bug 53552 Summary: Add support for !GCC$ warning directive (cf. #pragma warning) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53552 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE
[Bug fortran/53934] Better CPP macro diagnostics
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53934 --- Comment #2 from Manuel López-Ibáñez manu at gcc dot gnu.org --- How is Fortran using CPP? Does it preprocess the whole file externally and then passes it to the Fortran FE? If so, this is not going to work since the locations generated by macro expansion are only generated when preprocessing. If Fortran reads the already preprocessed file, then there are not macros at all. Fortran would need to do the preprocessing in-process like the C/C++ FEs to even start thinking about implementing this. Once that is done and PR44054 is fixed, then this should be trivial.
[Bug fortran/53934] Better CPP macro diagnostics
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53934 Manuel López-Ibáñez manu at gcc dot gnu.org changed: What|Removed |Added CC||manu at gcc dot gnu.org --- Comment #1 from Manuel López-Ibáñez manu at gcc dot gnu.org 2012-10-09 09:15:10 UTC --- (In reply to comment #0) Expected: Something similar. Possibly related to PR44054 and PR53552 See tree-diagnostic.c: maybe_unwind_expanded_macro_loc. You could reimplement it in gfortran using fortran diagnostics machinery. But if you reimplemented the gfortran diagnostics machinery in terms of the general diagnostics machinery, it will just work (and you will also fix those PRs). Note that the function does not use anything C/C++ specific, not even tree-specific.