public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/36771] Non-Standard addition for C_LOC and character strings
Date: Fri, 12 Dec 2008 16:20:00 -0000 [thread overview]
Message-ID: <20081212161907.17270.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36771-16432@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from burnus at gcc dot gnu dot org 2008-12-12 16:19 -------
I have the gut feeling that the program in comment 1 is valid, even though
gfortran, g95, ifort and NAG f95 reject it. See PR 38506.
Regarding the c_loc: I think that should be possible; I'm not 100% sure whether
there exists scenarios where it causes problems, but ad hoc I don't see any.
Patch:
--- resolve.c (Revision 142706)
+++ resolve.c
@@ -2165,7 +2165,7 @@ gfc_iso_c_func_interface (gfc_symbol *sy
if (args_sym->attr.dimension != 0
&& (args_sym->as && args_sym->as->rank == 0))
{
- gfc_error_now ("Allocatable variable '%s' used as a
"
+ gfc_notify_std (GFC_STD_F2003, "Allocatable variable
'%s' used as a "
"parameter to '%s' at %L must not be
"
"an array of zero size",
args_sym->name, sym->name,
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36771
next prev parent reply other threads:[~2008-12-12 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 14:59 [Bug fortran/36771] New: " brtnfld at hdfgroup dot org
2008-07-14 20:46 ` [Bug fortran/36771] " brtnfld at hdfgroup dot org
2008-12-12 16:20 ` burnus at gcc dot gnu dot org [this message]
2008-12-15 10:50 ` burnus at gcc dot gnu dot org
2008-12-15 16:53 ` brtnfld at hdfgroup dot org
2008-12-15 20:36 ` burnus at gcc dot gnu dot 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=20081212161907.17270.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: 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).