From: Jerry D <jvdelisle2@gmail.com>
To: Harald Anlauf <anlauf@gmx.de>, fortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fortran: name conflict between internal procedure and derived type [PR104351]
Date: Fri, 13 Oct 2023 13:06:58 -0700 [thread overview]
Message-ID: <cf67b06d-bc8a-4880-8274-83e456ea9659@gmail.com> (raw)
In-Reply-To: <104b9c70-5222-4d90-a1de-84ac3bee6258@gmx.de>
On 10/11/23 12:44 PM, Harald Anlauf wrote:
> Dear All,
>
> sorry for attaching the wrong patch - this time it is the correct one!
>
> Harald
>
> On 10/11/23 21:39, Harald Anlauf wrote:
>> Dear All,
>>
>> the attached trivial patch fixes (= catches) a forgotten corner-case
>> in the detection of a name conflict between an internal procedure and
>> a local declaration for the case that the latter is a derived type.
>> Another torture test by Gerhard... ;-) Used to ICE previously.
>>
>> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>>
>> Thanks,
>> Harald
>>
This one is OK as well. Once I found the right patch on the right email.
Regardless, both good to go.
Thanks,
Jerry
next prev parent reply other threads:[~2023-10-13 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 19:39 Harald Anlauf
2023-10-11 19:44 ` Harald Anlauf
2023-10-13 20:06 ` Jerry D [this message]
2023-10-13 20:00 ` Jerry D
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=cf67b06d-bc8a-4880-8274-83e456ea9659@gmail.com \
--to=jvdelisle2@gmail.com \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
/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).