From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Cc: abensonca@gmail.com
Subject: Chained modules in a testcase
Date: Thu, 19 Jan 2023 19:45:40 +0000 [thread overview]
Message-ID: <CAGkQGiKeWhVD=JjZnr3KazvPtVOMZbnzUDzSH7bV1d1nQYwRcw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
Hi,
Andrew Benson found a rather horrible bug in my finalization patch that
involved two separate module files and another containing both a module and
the main program. They must be compiled separately for the bug to appear.
This bug arises in finalization because some derived type function results
wind up with a derived type that has no proc_name for its namespace, which
causes gfc_get_derived_vtab to segfault.
file 1: iso.f90 which contains a module only.
file 2: dt.90 which uses module iso within one of the module contained
functions
file 3: ov.f90 which contains another module using iso and dt, again within
a module constrained function. It also contains the main program.
How do I deal with this in the testsuite? I have tried all manner of
combinations of dg-compile-aux-modules and dg-additional-sources to no
avail.
Cheers
Paul
next reply other threads:[~2023-01-19 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 19:45 Paul Richard Thomas [this message]
2023-01-19 20:36 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='CAGkQGiKeWhVD=JjZnr3KazvPtVOMZbnzUDzSH7bV1d1nQYwRcw@mail.gmail.com' \
--to=paul.richard.thomas@gmail.com \
--cc=abensonca@gmail.com \
--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).