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/55134] associate construct and assumed size array
Date: Tue, 30 Oct 2012 11:34:00 -0000 [thread overview]
Message-ID: <bug-55134-4-uwe0dLSKZH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55134-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55134
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-10-30
CC| |burnus at gcc dot gnu.org,
| |janus at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-10-30 11:34:37 UTC ---
>From the dump. gfortran first generates a deferred-shape array:
a.data = (void * restrict) &i[0];
That's fine. But instead of passing
foo (&a);
it should pass
foo (a.data);
In resolve.c's resolve_assoc_var, one properly sets sym->as->type =
AS_DEFERRED.
The problem is that the code assumes that if the variable is not a pointer, it
cannot be AS_DEFERRED. From trans-array.c's
gfc_conv_array_parameter:
7017 if (!sym->attr.pointer
7018 && sym->as
7019 && sym->as->type != AS_ASSUMED_SHAPE
7020 && sym->as->type != AS_ASSUMED_RANK
7021 && !sym->attr.allocatable)
7022 {
...
next prev parent reply other threads:[~2012-10-30 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 9:48 [Bug fortran/55134] New: " valeryweber at hotmail dot com
2012-10-30 11:34 ` burnus at gcc dot gnu.org [this message]
2012-10-31 17:23 ` [Bug fortran/55134] " burnus at gcc dot gnu.org
2012-10-31 17:24 ` 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-55134-4-uwe0dLSKZH@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).