public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/54784] [OOP] allocation of extended types with polymorphic allocatable members Date: Tue, 02 Oct 2012 23:44:00 -0000 [thread overview] Message-ID: <bug-54784-4-aQDXDTV032@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54784-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54784 janus at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|unassigned at gcc dot |janus at gcc dot gnu.org |gnu.org | --- Comment #5 from janus at gcc dot gnu.org 2012-10-02 23:43:42 UTC --- The following patch seems to cure the test case in comment 1, as well as both variants in comment 0: Index: gcc/fortran/trans-stmt.c =================================================================== --- gcc/fortran/trans-stmt.c (revision 192004) +++ gcc/fortran/trans-stmt.c (working copy) @@ -5145,7 +5145,9 @@ gfc_trans_allocate (gfc_code * code) dataref = actual->next->expr->ref; /* Make sure we go up through the reference chain to the _data reference, where the arrayspec is found. */ - while (dataref->next && dataref->next->type != REF_ARRAY) + while (!(dataref->type == REF_COMPONENT + && strcmp (dataref->u.c.component->name, "_data") == 0) + && dataref->next) dataref = dataref->next; if (dataref->u.c.component->as)
next prev parent reply other threads:[~2012-10-02 23:44 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-02 20:07 [Bug fortran/54784] New: [oop] " jkozdon at gmail dot com 2012-10-02 21:52 ` [Bug fortran/54784] [OOP] " janus at gcc dot gnu.org 2012-10-02 22:15 ` jkozdon at gmail dot com 2012-10-02 22:36 ` janus at gcc dot gnu.org 2012-10-02 22:46 ` janus at gcc dot gnu.org 2012-10-02 23:44 ` janus at gcc dot gnu.org [this message] 2012-10-03 10:38 ` janus at gcc dot gnu.org 2012-10-03 16:09 ` [Bug fortran/54784] [4.7/4.8 Regression] [OOP] wrong code in polymorphic allocation with SOURCE janus at gcc dot gnu.org 2012-10-08 16:23 ` sfilippone at uniroma2 dot it 2012-10-09 10:00 ` sfilippone at uniroma2 dot it 2012-10-10 11:49 ` janus at gcc dot gnu.org 2012-10-11 17:53 ` janus at gcc dot gnu.org 2012-10-11 17:58 ` janus at gcc dot gnu.org 2012-10-14 22:16 ` janus at gcc dot gnu.org 2012-10-14 22:27 ` janus at gcc dot gnu.org
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-54784-4-aQDXDTV032@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).