Hi Paul,

> The patch is OK for trunk.

thanks a lot. Will commit soon.


> PS While you are with us, are you intending to deal with the 14 PRs
> for which you are the assignee or will you unassign yourself?

Good point. I will look through them and see what I can do. In fact I
might have a bit of time for gfortran hacking in the coming weeks, but
I cannot promise anything ....

Cheers,
Janus




> On 5 November 2016 at 10:15, Janus Weil <ja...@gcc.gnu.org> wrote:
>> Hi all,
>>
>> here is a patch that I had submitted already in February (see
>> https://gcc.gnu.org/ml/fortran/2016-02/msg00011.html). Unfortunately
>> it was never approved and I got distracted with other things and
>> forgot about it.
>>
>> It's a diagnostics patch, which makes sure that the responsible flag
>> is printed in several warning messages (for which this was still
>> missing). As a small extra the patch also mentions the -Wpedantic flag
>> in the gfortran documentation.
>>
>> Fortunately the patch still applies cleanly and regtests without
>> failures on x86_64-linux-gnu. Ok for trunk?
>>
>> Cheers,
>> Janus
>>
>>
>> 2016-11-05  Janus Weil  <ja...@gcc.gnu.org>
>>         Manuel Lopez-Ibanez  <m...@gcc.gnu.org>
>>
>>     PR fortran/69495
>>     * invoke.texi: Mention -Wpedantic as an alias of -pedantic.
>>     * check.c (gfc_check_transfer): Mention responsible flag in warning
>>     message.
>>     * frontend-passes.c (do_warn_function_elimination): Ditto.
>>     * resolve.c (resolve_elemental_actual): Ditto.
>>     (resolve_operator): Ditto.
>>     (warn_unused_fortran_label): Ditto.
>>     * trans-common.c (translate_common): Ditto.
>>
>>
>> 2016-11-05  Janus Weil  <ja...@gcc.gnu.org>
>>         Dominique d'Humieres  <domi...@lps.ens.fr>
>>
>>     PR fortran/69495
>>     * gfortran.dg/elemental_optional_args_6.f90: Use -Wpedantic flag.
>
>
>
> --
> The difference between genius and stupidity is; genius has its limits.
>
> Albert Einstein

Reply via email to