From: Harald Anlauf <anlauf@gmx.de>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: fortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, committed] Fortran: fix diagnostics for SELECT RANK [PR100607]
Date: Sat, 3 Jun 2023 21:13:41 +0200 [thread overview]
Message-ID: <42157f0e-a2a7-7bf0-5dbd-3904761c2fc6@gmx.de> (raw)
In-Reply-To: <CAGkQGiLn0EoC-GmOMAL1OARWRyBJO_atqa=0FBNYhQ_BbHX49g@mail.gmail.com>
Hi Paul,
On 6/3/23 07:48, Paul Richard Thomas via Gcc-patches wrote:
> Hi Harald,
>
> It looks good to me. Thanks to you and Steve for the fix. I suggest
> that it is such and obvious one that it deserved back-porting.
alright, I'll check how far this makes sense.
Cheers,
Harald
> Cheers
>
> Paul
>
> On Fri, 2 Jun 2023 at 19:06, Harald Anlauf via Fortran
> <fortran@gcc.gnu.org> wrote:
>>
>> Dear all,
>>
>> I've committed that attached simple patch on behalf of Steve
>> after discussion in the PR and regtesting on x86_64-pc-linux-gnu.
>>
>> It fixes a duplicate error message and an ICE.
>>
>> Pushed as r14-1505-gfae09dfc0e6bf4cfe35d817558827aea78c6426f .
>>
>> Thanks,
>> Harald
>>
>
>
WARNING: multiple messages have this Message-ID
From: Harald Anlauf <anlauf@gmx.de>
To: fortran@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Cc: fortran@gcc.gnu.org
Subject: Re: [PATCH, committed] Fortran: fix diagnostics for SELECT RANK [PR100607]
Date: Sat, 3 Jun 2023 21:13:41 +0200 [thread overview]
Message-ID: <42157f0e-a2a7-7bf0-5dbd-3904761c2fc6@gmx.de> (raw)
Message-ID: <20230603191341.o0EAiP2PQW8ev7WURMEgcRnulnuwGOVMUkZ2w5s7JsA@z> (raw)
In-Reply-To: <CAGkQGiLn0EoC-GmOMAL1OARWRyBJO_atqa=0FBNYhQ_BbHX49g@mail.gmail.com>
Hi Paul,
On 6/3/23 07:48, Paul Richard Thomas via Gcc-patches wrote:
> Hi Harald,
>
> It looks good to me. Thanks to you and Steve for the fix. I suggest
> that it is such and obvious one that it deserved back-porting.
alright, I'll check how far this makes sense.
Cheers,
Harald
> Cheers
>
> Paul
>
> On Fri, 2 Jun 2023 at 19:06, Harald Anlauf via Fortran
> <fortran@gcc.gnu.org> wrote:
>>
>> Dear all,
>>
>> I've committed that attached simple patch on behalf of Steve
>> after discussion in the PR and regtesting on x86_64-pc-linux-gnu.
>>
>> It fixes a duplicate error message and an ICE.
>>
>> Pushed as r14-1505-gfae09dfc0e6bf4cfe35d817558827aea78c6426f .
>>
>> Thanks,
>> Harald
>>
>
>
next prev parent reply other threads:[~2023-06-03 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 18:05 Harald Anlauf
2023-06-03 5:48 ` Paul Richard Thomas
2023-06-03 19:13 ` Harald Anlauf [this message]
2023-06-03 19:13 ` Harald Anlauf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42157f0e-a2a7-7bf0-5dbd-3904761c2fc6@gmx.de \
--to=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).