From: Harald Anlauf <anlauf@gmx.de>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>,
Damian Rouson <damian@sourceryinstitute.org>
Subject: Re: [Patch, fortran PR89645/99065 No IMPLICIT type error with: ASSOCIATE( X => function() )
Date: Tue, 12 Mar 2024 22:07:09 +0100 [thread overview]
Message-ID: <e51063d4-8add-4966-85bf-ceb52c2241d0@gmx.de> (raw)
In-Reply-To: <CAGkQGi+-jb6-6emb+XG4rhXy1MRr7u_X_OhQ4NBmpLgkja9EDA@mail.gmail.com>
Hi Paul,
On 3/12/24 15:54, Paul Richard Thomas wrote:
> Hi All,
>
> This is the last posting of this patch before I push it. Harald is OK with
> it on the grounds that the inferred_type flag guards the whole lot,
> except for the chunks in trans-stmt.cc.
>
> In spite of Harald's off-list admonition not to try to fix everything at
> once, this version fixes most of the inquiry reference bugs
> (associate_68.f90) with the exception of character(kind=4) function
> selectors. The reason for this is that I have some housekeeping to do
> before release on finalization and then I want to replace this patch in
> 15-branch with two pass parsing. My first attempts at the latter were a
> partial success.
you wouldn't stop trying to fix everything, would you? ;-)
> It regtests OK on x86_64. Unless there are objections, I will commit on
> Thursday evening.
No objections, just one wish: could you improve the text of the
following comments so that mere mortals understand them?
diff --git a/gcc/fortran/primary.cc b/gcc/fortran/primary.cc
index 12e7bf3c873..0ab69bb9dce 100644
--- a/gcc/fortran/primary.cc
+++ b/gcc/fortran/primary.cc
[...]
+ /* If there is a usable inquiry reference not there are no matching
+ derived types, force the inquiry reference by setting unknown the
+ type of the primary expression. */
I have a hard time parsing the first part of that sentence.
diff --git a/gcc/fortran/symbol.cc b/gcc/fortran/symbol.cc
index 5d9852c79e0..16adb2a7efb 100644
--- a/gcc/fortran/symbol.cc
+++ b/gcc/fortran/symbol.cc
[...]
+/* Find all derived types in the uppermost namespace that have a component
+ a component called name and stash them in the assoc field of an
+ associate name variable.
"a component" too much?
Thanks,
Harald
> Cheers
>
> Paul
next prev parent reply other threads:[~2024-03-12 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 17:26 Paul Richard Thomas
2024-01-08 21:53 ` Harald Anlauf
2024-03-03 16:04 ` Paul Richard Thomas
2024-03-03 20:20 ` Harald Anlauf
2024-03-12 14:54 ` Paul Richard Thomas
2024-03-12 21:07 ` Harald Anlauf [this message]
2024-03-12 21:28 ` Paul Richard Thomas
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=e51063d4-8add-4966-85bf-ceb52c2241d0@gmx.de \
--to=anlauf@gmx.de \
--cc=damian@sourceryinstitute.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
--cc=sgk@troutmask.apl.washington.edu \
/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).