public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/52052] New: [Coarray] Properly handle coarray components of derived types Date: Mon, 30 Jan 2012 14:26:00 -0000 [thread overview] Message-ID: <bug-52052-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52052 Bug #: 52052 Summary: [Coarray] Properly handle coarray components of derived types Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org Special care needs to be taken with coarrays - and in particular coarray components; they may only be collectively allocated and deallocated. In particular: Intrinsic assignment: Contrary to normal allocatable components, no reallocation is allowed. The programmer guarantees that the shape and type parameters are suitable. Caveat: Be aware of allocatable components nested within coarray components - and issues with polymorphism. Please also check that: - Calling caf_register is done with ALLOCATE, also with SOURCE= - Calling of caf_deregister when leaving the scope/calling DEALLOCATE - Special handling of polymorphic coarray components - Whether there are issues regarding _def_init and _copy; cf. PR 51947. Consider whether a simple INTENT_INOUT for _copy would be more appropriate. - Check that there is indeed no realloc on assignment for coarray variables.
next reply other threads:[~2012-01-30 14:13 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-30 14:26 burnus at gcc dot gnu.org [this message] 2013-07-22 17:29 ` [Bug fortran/52052] " burnus at gcc dot gnu.org 2013-07-22 17:31 ` burnus at gcc dot gnu.org 2015-10-20 16:20 ` dominiq at lps dot ens.fr
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-52052-4@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: linkBe 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).