public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104573] ICE in resolve_structure_cons, at fortran/resolve.cc:1299
Date: Wed, 16 Feb 2022 20:39:00 +0000 [thread overview]
Message-ID: <bug-104573-4-WzuuZWCqZC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104573-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104573
--- Comment #5 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Wed, Feb 16, 2022 at 08:32:25PM +0000, anlauf at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104573
>
> --- Comment #4 from anlauf at gcc dot gnu.org ---
> (In reply to Steve Kargl from comment #3)
> > I'm not sure. I don't use CLASSes, so only know a bit
> > about them. If I check F18:7.5.6, I find
> >
> > C786 (R753) A final-subroutine-name shall be the name of a moduler
> > procedure with exactly one dummy argument. That argument shall
> > be nonoptional and shall be a noncoarray, nonpointer, nonallocatable,
> > *** nonpolymorphic ***
> > variable of the derived type being defined. All length type
> > parameters of the dummy argument shall be assumed. The dummy
> > argument shall not have the INTENT (OUT) or VALUE attribute.
>
> Steve, there's no finalization referred to in this PR.
> Can you please recheck?
>
Ah dang. I conflated PR 104572, to which I just posted a patch,
with this PR. Your patch is then likely the correct approach.
Sorry about any confusion.
next prev parent reply other threads:[~2022-02-16 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 17:35 [Bug fortran/104573] New: " gscfq@t-online.de
2022-02-16 20:00 ` [Bug fortran/104573] " kargl at gcc dot gnu.org
2022-02-16 20:10 ` anlauf at gcc dot gnu.org
2022-02-16 20:25 ` sgk at troutmask dot apl.washington.edu
2022-02-16 20:32 ` anlauf at gcc dot gnu.org
2022-02-16 20:39 ` sgk at troutmask dot apl.washington.edu [this message]
2022-02-16 20:59 ` anlauf at gcc dot gnu.org
2022-02-16 21:20 ` anlauf at gcc dot gnu.org
2022-03-02 18:23 ` cvs-commit at gcc dot gnu.org
2022-03-02 18:25 ` anlauf at gcc dot gnu.org
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=bug-104573-4-WzuuZWCqZC@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).