PING - https://gcc.gnu.org/ml/gcc-patches/2014-12/msg00731.html
Tobias Burnus wrote: > This patch requires that the gfc_error patch has been applied, > https://gcc.gnu.org/ml/gcc-patches/2014-12/msg00607.html That patch has now been committed - and my patch still applies, building and regtesting still succeeds without new failures poping up. > The patch does some missing '%s' to %qs and '...' to %<...%> for gfc_error, > does likewise for gfc_notify_std and converts the latter into calls to > gfc_error and gfc_warning * * * Side note: The biggest remaining issue with regards to using the common diagnostic is supporting two locations. For the current plans, see: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44054#c22 Other remaining items: * Things supported by Fortran and not by the common diagnostic, e.g. "<During initialization>", but that requires some careful review what's missing and whether it matters. * Option handling: PR54687. One could also think of adding "error (OPT_..." support, printing the option in brackets (like: "[-std=f95]"). On the other hand, as that's all what the feature would do (contrary to -W... which also enters in -Werror=...), one could simply leave that in the error calling part. Currently, the Fortran code doesn't print this; printing it with gfc_notify_std for -std= would be trivial. See also PR31601. * libcpp-related features such as macro expansion tracking. Requires libcpp whitespace support, cf. PR64273 and links there in. And PR45179 (support unicode in 4_"..." strings) also depends on the libcpp work. Tobias
