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/64945] New: Structure constructors and non-NULL-data-targets and polymorphic pointer components Date: Thu, 05 Feb 2015 08:44:00 -0000 [thread overview] Message-ID: <bug-64945-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64945 Bug ID: 64945 Summary: Structure constructors and non-NULL-data-targets and polymorphic pointer components Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: pault at gcc dot gnu.org Follow up to PR64757 and https://gcc.gnu.org/ml/fortran/2015-02/msg00022.html The patch for PR64757 handles polymorphic allocatable components with structure constructors. [Somewhat related PR50438, PR39988, PR49213] I am pretty sure, we need to do likewise with pointer components (class => class but also class <-> type). (See also raw patch at PR39988, which I haven't checked what exactly it fixes.)
next reply other threads:[~2015-02-05 8:44 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-05 8:44 burnus at gcc dot gnu.org [this message] 2015-10-09 21:49 ` [Bug fortran/64945] " 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-64945-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).