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/46017] New: Reject ALLOCATE(a, a%b) as "a%b" depends on the allocation status of "a" Date: Thu, 14 Oct 2010 12:17:00 -0000 [thread overview] Message-ID: <bug-46017-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46017 Summary: Reject ALLOCATE(a, a%b) as "a%b" depends on the allocation status of "a" Product: gcc Version: 4.6.0 Status: UNCONFIRMED Keywords: diagnostic Severity: enhancement Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org Follow up to PR 42647 comment 11 allocate(a1, a1%b1, a1%b1%c1) is invalid as it violates: "An allocate-object [...] shall not depend [...] on the [...] allocation status [...] of any allocate-object in the same ALLOCATE statement." (F2008, "6.7.1 ALLOCATE statement" first paragraph after C644.) The solution is to write three independent ALLOCATE statements. I think this particular case could be compile-time detectable. Cf. also http://gcc.gnu.org/ml/fortran/2010-10/msg00159.html (contains quote from the F2003 handbook.) Full test case: PR 42647 comment 10
next reply other threads:[~2010-10-14 12:17 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-14 12:17 burnus at gcc dot gnu.org [this message] 2010-12-29 2:57 ` [Bug fortran/46017] " dfranke at gcc dot gnu.org 2011-01-01 22:26 ` tkoenig at gcc dot gnu.org 2011-01-05 10:03 ` tkoenig at gcc dot gnu.org 2011-01-08 22:49 ` tkoenig 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-46017-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).