public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/45516] [F08] allocatable compontents of recursive type Date: Fri, 03 Sep 2010 09:59:00 -0000 [thread overview] Message-ID: <20100903095902.28241.qmail@sourceware.org> (raw) In-Reply-To: <bug-45516-16146@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from janus at gcc dot gnu dot org 2010-09-03 09:59 ------- Here is a patch to accept the type declaration in comment #0: Index: decl.c =================================================================== --- decl.c (revision 163798) +++ decl.c (working copy) @@ -1494,11 +1494,11 @@ build_struct (const char *name, gfc_charlen *cl, g gfc_component *c; gfc_try t = SUCCESS; - /* F03:C438/C439. If the current symbol is of the same derived type that we're - constructing, it must have the pointer attribute. */ + /* F08:C440. If the current symbol is of the same derived type that we're + constructing, it must be POINTER or ALLOCATABLE. */ if ((current_ts.type == BT_DERIVED || current_ts.type == BT_CLASS) && current_ts.u.derived == gfc_current_block () - && current_attr.pointer == 0) + && !current_attr.pointer && !current_attr.allocatable) { gfc_error ("Component at %C must have the POINTER attribute"); return FAILURE; -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45516
next prev parent reply other threads:[~2010-09-03 9:59 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-09-03 9:57 [Bug fortran/45516] New: " janus at gcc dot gnu dot org 2010-09-03 9:59 ` janus at gcc dot gnu dot org [this message] 2010-09-03 12:12 ` [Bug fortran/45516] " burnus at gcc dot gnu dot org [not found] <bug-45516-4@http.gcc.gnu.org/bugzilla/> 2011-02-03 22:03 ` janus at gcc dot gnu.org 2011-02-06 12:36 ` janus at gcc dot gnu.org 2011-02-06 13:02 ` janus at gcc dot gnu.org 2012-08-29 9:18 ` burnus at gcc dot gnu.org 2020-10-21 12:39 ` cvs-commit 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=20100903095902.28241.qmail@sourceware.org \ --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).