From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: fortran@gcc.gnu.org
Subject: finalization issue
Date: Wed, 3 May 2023 15:58:58 -0700 [thread overview]
Message-ID: <ZFLnMkSG95YXRUxw@troutmask.apl.washington.edu> (raw)
All,
PR97122 shows an issue with finalization.
It seems I attached a diff to the PR in 2020,
which allows the code to compile. The diff
applied to today's trunk still allows the
code to compile but there is now at least
1 regression with finalize_8.f03.
Even with my patch, I'm uncertain as to
whether the finalizing subroutine is
correctly hooked to the right namespace.
--
steve
next reply other threads:[~2023-05-03 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 22:58 Steve Kargl [this message]
2023-05-04 8:09 ` Paul Richard Thomas
2023-05-04 14:44 ` Steve Kargl
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=ZFLnMkSG95YXRUxw@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@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).