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/56305] passing array of character with len>1 to c_loc
Date: Wed, 13 Feb 2013 12:20:00 -0000 [thread overview]
Message-ID: <bug-56305-4-YZLoQqMRcA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56305-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56305
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-02-13 12:19:39 UTC ---
> The following code compiles, but shouldnt it be rejected?
It seems to be invalid Fortran 2003 but valid Fortran 2008 (w/ and w/o
TS29113). The gfortran's diagnostic handling for C_LOC still needs some changes
for -std=f2003, -std=f2008, -std=f2008ts (rejecting too much, some diagnostic
missing for -std=f2003).
Fortran 2003 has ("15.1.2.5 C LOC (X)"):
"Argument. X shall either
(1) have interoperable type and type parameters and be [...]
(2) be a nonpolymorphic scalar, have no length type parameters, and be [...]"
A type parameter of len=2 is not valid and also "c" is not a scalar – Thus, it
seems to be invalid.
However, it seems to be valid with Fortran 2008 ("15.2.3.6 C LOC (X)"); note
the change "type parameter" to "kind type parameter"
"Argument. X shall have either the POINTER or TARGET attribute. It shall not be
a coindexed object. It shall either be a variable with interoperable type and
kind type parameters, or be a scalar, nonpolymorphic variable with no length
type parameters. If it is allocatable, it shall be allocated. If it is a
pointer, it shall be associated. If it is an array, it shall be contiguous and
have nonzero size. It shall not be a zero-length string."
TS 29113 changes the latter as follows:
"{In 15.2.3.6 C_LOC(X), paragraph 3}
Delete 'scalar,'."
next prev parent reply other threads:[~2013-02-13 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 11:24 [Bug fortran/56305] New: " valeryweber at hotmail dot com
2013-02-13 12:20 ` burnus at gcc dot gnu.org [this message]
2013-03-20 14:42 ` [Bug fortran/56305] " burnus at gcc dot gnu.org
2013-03-21 21:43 ` burnus 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-56305-4-YZLoQqMRcA@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).