public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/59265] [4.9 Regression] Segmentation fault in ipa_note_param_call for -fprofile-use in SPEC CPU2006
Date: Sun, 15 Dec 2013 16:32:00 -0000 [thread overview]
Message-ID: <bug-59265-4-eusjEloKrY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59265-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59265
--- Comment #4 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Index: ipa-prop.c
===================================================================
--- ipa-prop.c (revision 205941)
+++ ipa-prop.c (working copy)
@@ -2022,9 +2022,18 @@
struct param_analysis_info *parms_ainfo, gimple call)
{
tree target = gimple_call_fn (call);
+ struct cgraph_edge *cs;
- if (!target)
+ if (!target
+ || (TREE_CODE (target) != SSA_NAME
+ && !virtual_method_call_p (target)))
return;
+
+ /* If we previously turned the call into a direct call, there is
+ no need to analyze. */
+ cs = cgraph_edge (node, call);
+ if (cs && !cs->indirect_unknown_callee)
+ return;
if (TREE_CODE (target) == SSA_NAME)
ipa_analyze_indirect_call_uses (node, info, parms_ainfo, call, target);
else if (virtual_method_call_p (target))
Patch I am testing...
next prev parent reply other threads:[~2013-12-15 16:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 17:57 [Bug c++/59265] New: " marxin.liska at gmail dot com
2013-11-25 9:19 ` [Bug ipa/59265] [4.9 Regression] " rguenth at gcc dot gnu.org
2013-12-14 13:39 ` octoploid at yandex dot com
2013-12-14 20:35 ` octoploid at yandex dot com
2013-12-15 16:00 ` hubicka at gcc dot gnu.org
2013-12-15 16:32 ` hubicka at gcc dot gnu.org [this message]
2013-12-15 22:19 ` hubicka at gcc dot gnu.org
2013-12-16 6:16 ` octoploid at yandex dot com
2013-12-16 8:02 ` octoploid at yandex dot com
2013-12-16 8:48 ` octoploid at yandex dot com
2013-12-16 11:14 ` hubicka at gcc dot gnu.org
2013-12-16 12:04 ` octoploid at yandex dot com
2013-12-16 13:20 ` hubicka at gcc dot gnu.org
2013-12-16 13:37 ` hubicka at gcc dot gnu.org
2013-12-16 13:41 ` hubicka at gcc dot gnu.org
2013-12-16 15:08 ` octoploid at yandex dot com
2013-12-16 17:51 ` hubicka at ucw dot cz
2013-12-16 20:32 ` trippels at gcc dot gnu.org
2013-12-16 21:13 ` hubicka at ucw dot cz
2013-12-16 21:32 ` trippels at gcc dot gnu.org
2013-12-16 21:50 ` hubicka at ucw dot cz
2013-12-17 13:01 ` trippels at gcc dot gnu.org
2013-12-17 21:25 ` trippels at gcc dot gnu.org
2013-12-18 9:14 ` trippels 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-59265-4-eusjEloKrY@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).