public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/107635] New: [Coarray] Allocatable components of types defined in module's interface are not handled correctly when used in coarrays.
@ 2022-11-11 14:03 vehre at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: vehre at gcc dot gnu.org @ 2022-11-11 14:03 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107635
Bug ID: 107635
Summary: [Coarray] Allocatable components of types defined in
module's interface are not handled correctly when used
in coarrays.
Product: gcc
Version: 11.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: vehre at gcc dot gnu.org
Target Milestone: ---
Created attachment 53881
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53881&action=edit
Example demonstrating the issue.
When defining a type with an allocatable component in a module's interface (it
doesn't really matter where the implementation is given either in the same
module or a submodule) and using gfortran with -fcoarray=lib (for example in
combination with opencoarrays), then the alloc.comp. is not treated correctly
when used in a coarray. The issue is, that during internal type generation the
coarray attr is not set for the type and therefore no member for the
(sub-)caf_token is assigned. This leads to segfaults in the calling code. See
attached example and issue
https://github.com/sourceryinstitute/OpenCoarrays/issues/739 from opencoarrays.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-11-11 14:03 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-11 14:03 [Bug fortran/107635] New: [Coarray] Allocatable components of types defined in module's interface are not handled correctly when used in coarrays vehre at gcc dot gnu.org
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).