public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian_harvey at bigpond dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/48478] New: Valid array-constructor syntax rejected/invalid accepted
Date: Wed, 06 Apr 2011 11:51:00 -0000 [thread overview]
Message-ID: <bug-48478-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48478
Summary: Valid array-constructor syntax rejected/invalid
accepted
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: ian_harvey@bigpond.com
Created attachment 23898
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23898
Demonstrates valid and invalid syntax
gfortran 4.7 compiled from trunk revision 171951 rejects an array constructor
with syntax:
[ derived_type_name:: ... ]
With -Wall --std=f2003 it accepts without complaint one of the form:
[ TYPE(derived_type_name):: ... ]
>From F2008 draft:
R468: array-constructor is (/ ac-spec /)
or lbracket ac-spec rbracket
R469: ac-spec is type-spec ::
or [type-spec ::] ac-value-list
R402: type-spec is intrinsic-type-spec
or derived-type-spec
R453: derived-type-spec is type-name [(type-param-spec-list)]
It looks like the compiler has confused a type-spec with a
declaration-type-spec, (which does use the TYPE keyword).
next reply other threads:[~2011-04-06 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 11:51 ian_harvey at bigpond dot com [this message]
2011-04-06 13:20 ` [Bug fortran/48478] Array-constructor with type-spec: reject valid/accept invalid burnus at gcc dot gnu.org
2015-02-25 10:35 ` fxcoudert 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-48478-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: link
Be 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).