public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matt at use dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/55264] [4.6/4.7/4.8 Regression] ICE: in ipa_make_edge_direct_to_target, at ipa-prop.c:2141 with -O2 -fno-early-inlining -fno-weak
Date: Tue, 19 Feb 2013 22:52:00 -0000 [thread overview]
Message-ID: <bug-55264-4-6rmuBeWXd2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55264-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55264
Matt Hargett <matt at use dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matt at use dot net
--- Comment #15 from Matt Hargett <matt at use dot net> 2013-02-19 22:51:57 UTC ---
Hey Martin,
I noticed that this doesn't apply cleanly to google/4_7 without some massaging.
The difference between trunk and google/4_7 might be worth pulling into trunk.
Unfortunately, the trail of merge commit log breadcrumbs leads to a dead end :/
>From a blame of google/main/gcc/ipa.c:
165972 hubicka || (before_inlining_p
195116 davidxl && DECL_VIRTUAL_P (node->symbol.decl)
195825 davidxl && cgraph_is_aux_decl_external (node))))
it's that last line that's unique to the google branches, and should probably
be merged to trunk.
next prev parent reply other threads:[~2013-02-19 22:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 14:08 [Bug tree-optimization/55264] New: " zsojka at seznam dot cz
2012-11-10 17:08 ` [Bug tree-optimization/55264] " mpolacek at gcc dot gnu.org
2012-11-21 16:58 ` aldyh at gcc dot gnu.org
2012-11-27 15:34 ` aldyh at gcc dot gnu.org
2012-11-28 14:16 ` aldyh at gcc dot gnu.org
2012-12-07 9:33 ` rguenth at gcc dot gnu.org
2013-01-03 16:30 ` hubicka at gcc dot gnu.org
2013-01-08 18:17 ` jamborm at gcc dot gnu.org
2013-01-09 10:36 ` jamborm at gcc dot gnu.org
2013-01-09 15:24 ` hubicka at ucw dot cz
2013-01-10 18:03 ` jamborm at gcc dot gnu.org
2013-01-10 18:15 ` jamborm at gcc dot gnu.org
2013-01-17 11:43 ` jamborm at gcc dot gnu.org
2013-01-21 17:02 ` jamborm at gcc dot gnu.org
2013-01-21 17:10 ` jamborm at gcc dot gnu.org
2013-01-21 17:11 ` jamborm at gcc dot gnu.org
2013-02-19 22:52 ` matt at use dot net [this message]
2013-02-20 13:37 ` 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-55264-4-6rmuBeWXd2@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).