public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49708] [4.5/4.6/4.7 Regression] ICE with allocate and no dimensions
Date: Tue, 12 Jul 2011 12:28:00 -0000 [thread overview]
Message-ID: <bug-49708-4-tPQYwbXY9H@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49708-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49708
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2011.07.12 12:27:33
Ever Confirmed|0 |1
--- Comment #2 from janus at gcc dot gnu.org 2011-07-12 12:27:33 UTC ---
(In reply to comment #1)
> In principle, the check is still in resolve.c - the question is: Why doesn't it
> trigger?
Apparently because of the pointer attribute. Changing "pointer" to
"allocatable" in the test case will trigger the error message.
With the following patch one also gets the error message for the pointer case,
but I haven't checked if this breaks anything else:
Index: gcc/fortran/resolve.c
===================================================================
--- gcc/fortran/resolve.c (revision 175788)
+++ gcc/fortran/resolve.c (working copy)
@@ -6884,7 +6884,7 @@ resolve_allocate_expr (gfc_expr *e, gfc_code *code
gfc_find_derived_vtab (ts.u.derived);
}
- if (pointer || (dimension == 0 && codimension == 0))
+ if (dimension == 0 && codimension == 0)
goto success;
/* Make sure the last reference node is an array specifiction. */
next prev parent reply other threads:[~2011-07-12 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 23:38 [Bug fortran/49708] New: internal compiler error " fnordxyz at yahoo dot com
2011-07-12 8:38 ` [Bug fortran/49708] [4.5/4.6/4.7 Regression] ICE " burnus at gcc dot gnu.org
2011-07-12 12:28 ` janus at gcc dot gnu.org [this message]
2011-07-12 12:39 ` janus at gcc dot gnu.org
2011-07-12 14:45 ` janus at gcc dot gnu.org
2011-07-18 7:34 ` burnus at gcc dot gnu.org
2011-07-18 17:09 ` janus at gcc dot gnu.org
2011-07-19 12:42 ` janus at gcc dot gnu.org
2011-07-22 22:24 ` janus at gcc dot gnu.org
2011-07-23 14:45 ` janus at gcc dot gnu.org
2011-07-23 14:53 ` janus 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-49708-4-tPQYwbXY9H@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).