public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64528] [5 Regression] ICE: in process_constraint, at tree-ssa-structalias.c:3002 with -O -fno-tree-ccp -fno-tree-dce
Date: Mon, 12 Jan 2015 15:21:00 -0000 [thread overview]
Message-ID: <bug-64528-4-f4uURbEm7f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64528-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64528
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
Component|tree-optimization |fortran
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'd say this is a Fortran FE bug.
The reason this ICEs is that the inliner emits 10 = 11; statement (with
INTEGER_CST on lhs), but that happens because myint PARM_DECL is TREE_READONLY,
which looks wrong when it clearly is assigned to.
The setting of TREE_READONLY happens in trans-decl.c:
2330 /* All implementation args are read-only. */
2331 TREE_READONLY (parm) = 1;
That looks just wrong at least for some f->sym->attr.value dummy arguments ==
PARM_DECLs, perhaps all?
next prev parent reply other threads:[~2015-01-12 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-64528-4@http.gcc.gnu.org/bugzilla/>
2015-01-09 11:20 ` [Bug tree-optimization/64528] " rguenth at gcc dot gnu.org
2015-01-12 14:48 ` jakub at gcc dot gnu.org
2015-01-12 15:21 ` jakub at gcc dot gnu.org [this message]
2015-01-13 12:50 ` [Bug fortran/64528] " rguenth at gcc dot gnu.org
2015-01-13 16:43 ` jakub at gcc dot gnu.org
2015-01-14 15:26 ` rguenth at gcc dot gnu.org
2015-01-14 20:23 ` jakub at gcc dot gnu.org
2015-02-01 21:52 ` jakub 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-64528-4-f4uURbEm7f@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).