public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikael at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41298] wrong-code: Default initializer C_NULL_PTR ignored
Date: Wed, 09 Sep 2009 20:42:00 -0000 [thread overview]
Message-ID: <20090909204134.6364.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41298-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from mikael at gcc dot gnu dot org 2009-09-09 20:41 -------
(In reply to comment #1)
> Thus the question is: Why is the last expr == NULL and not EXPR_VARIABLE of
> flavour FL_PARAMETER?
gfc_match_rvalue replaces parameters with their values:
case FL_PARAMETER:
/* A statement of the form "REAL, parameter :: a(0:10) = 1" will
end up here. Unfortunately, sym->value->expr_type is set to
EXPR_CONSTANT, and so the if () branch would be followed without
the !sym->as check. */
if (sym->value && sym->value->expr_type != EXPR_ARRAY && !sym->as)
e = gfc_copy_expr (sym->value);
Then why is the value a NULL expr?
Because that's how we recognise c_null(_fun)?_ptr at resolution time.
See the comment in gen_special_c_interop_ptr:
/* Create a constructor with no expr, that way we can recognize if the user
tries to call the structure constructor for one of the iso_c_binding
derived types during resolution (resolve_structure_cons). */
tmp_sym->value->value.constructor = gfc_get_constructor ();
So, it's a feature ;)
Tried a bit, but no idea how to fix it.
--
mikael at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2009-09-09 20:41:34
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41298
next prev parent reply other threads:[~2009-09-09 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 16:24 [Bug fortran/41298] New: wrong-code: Default initializer ignored burnus at gcc dot gnu dot org
2009-09-08 16:07 ` [Bug fortran/41298] wrong-code: Default initializer C_NULL_PTR ignored burnus at gcc dot gnu dot org
2009-09-09 20:42 ` mikael at gcc dot gnu dot org [this message]
2009-09-10 1:09 ` jvdelisle at gcc dot gnu dot org
2009-09-10 2:44 ` kargl at gcc dot gnu dot org
2009-12-13 16:22 ` dfranke at gcc dot gnu dot org
2010-01-06 21:49 ` burnus at gcc dot gnu dot org
2010-01-09 9:12 ` burnus at gcc dot gnu dot org
2010-01-09 9:12 ` burnus at gcc dot gnu dot org
2010-02-07 4:02 ` hjl dot tools at gmail dot com
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=20090909204134.6364.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).