public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/46823] [4.6 Regression] ICE: edge points to wrong declaration
Date: Fri, 07 Jan 2011 18:21:00 -0000 [thread overview]
Message-ID: <bug-46823-4-vKec2q131N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46823-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46823
--- Comment #10 from Jan Hubicka <hubicka at ucw dot cz> 2011-01-07 18:13:33 UTC ---
> Basically what happens that cgraph_node (decl) and e->callee have the
> same former_clone_of one is not clone of each other. I am now about
> to investigate how exactly this appears in the IL to be sure it can
> actually happen legitimately.
Hmm, how this happens? The call statement should not point to clones
since it should stay intact from early optimization.
Honza
next prev parent reply other threads:[~2011-01-07 18:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 15:22 [Bug other/46823] New: " marc.glisse at normalesup dot org
2010-12-06 18:55 ` [Bug middle-end/46823] [4.6 Regression] " hjl.tools at gmail dot com
2010-12-07 13:13 ` jamborm at gcc dot gnu.org
2010-12-07 13:15 ` jamborm at gcc dot gnu.org
2010-12-07 13:29 ` jamborm at gcc dot gnu.org
2010-12-09 13:28 ` jamborm at gcc dot gnu.org
2010-12-16 17:55 ` jamborm at gcc dot gnu.org
2011-01-03 17:41 ` jamborm at gcc dot gnu.org
2011-01-03 20:34 ` rguenth at gcc dot gnu.org
2011-01-07 13:26 ` jamborm at gcc dot gnu.org
2011-01-07 17:17 ` jamborm at gcc dot gnu.org
2011-01-07 18:21 ` hubicka at ucw dot cz [this message]
2011-01-07 21:07 ` hubicka at gcc dot gnu.org
2011-01-08 0:23 ` marc.glisse at normalesup dot org
2011-01-08 0:35 ` hubicka at gcc dot gnu.org
2011-01-08 2:21 ` hubicka at gcc dot gnu.org
2011-01-08 4:17 ` hubicka at gcc dot gnu.org
2011-01-10 21:02 ` jamborm at gcc dot gnu.org
2011-01-11 13:37 ` hubicka at gcc dot gnu.org
2011-01-12 14:01 ` jamborm at gcc dot gnu.org
2011-01-13 10:55 ` rguenth at gcc dot gnu.org
2011-01-13 12:28 ` jamborm at gcc dot gnu.org
2011-01-13 16:57 ` hubicka at ucw dot cz
2011-01-14 12:10 ` jamborm at gcc dot gnu.org
2011-01-14 12:40 ` jamborm 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-46823-4-vKec2q131N@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).