public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "octoploid at yandex dot com" <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: Mon, 16 Dec 2013 08:48:00 -0000 [thread overview] Message-ID: <bug-59265-4-pqdoDKxyLb@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 #9 from Markus Trippelsdorf <octoploid at yandex dot com> --- Maybe something like this: diff --git a/gcc/ipa-profile.c b/gcc/ipa-profile.c index ef9e24224921..66f87816e1bf 100644 --- a/gcc/ipa-profile.c +++ b/gcc/ipa-profile.c @@ -210,6 +210,8 @@ ipa_profile_generate_summary (void) if (h->hvalue.counters[2]) { struct cgraph_edge * e = cgraph_edge (node, stmt); + if (e && !e->indirect_unknown_callee) + break; e->indirect_info->common_target_id = h->hvalue.counters [0]; e->indirect_info->common_target_probability Seems to fix Mozilla build untill the next (unrelated) ICE: /var/tmp/mozilla-central/js/src/vm/Stack.cpp: In member function ‘operator++’: /var/tmp/mozilla-central/js/src/vm/Stack.cpp:717:1: internal compiler error: in fixup_reorder_chain, at cfgrtl.c:3739 } ^ 0x5b594c fixup_reorder_chain ../../gcc/gcc/cfgrtl.c:3738 0x5b594c cfg_layout_finalize() ../../gcc/gcc/cfgrtl.c:4295 0xd42eb2 duplicate_computed_gotos ../../gcc/gcc/bb-reorder.c:2492 0xd42eb2 execute ../../gcc/gcc/bb-reorder.c:2524 Please submit a full bug report, >From gcc-bugs-return-437689-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 16 08:51:39 2013 Return-Path: <gcc-bugs-return-437689-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 27364 invoked by alias); 16 Dec 2013 08:51:38 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 27347 invoked by uid 48); 16 Dec 2013 08:51:35 -0000 From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59522] "cc1plus: error:=?UTF-8?Q? unrecognized command line option ‘-fmy-loop-block’ ?=" is generated when g++ is run but not with cc1plus Date: Mon, 16 Dec 2013 08:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution Message-ID: <bug-59522-4-KoiTA8NWS6@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59522-4@http.gcc.gnu.org/bugzilla/> References: <bug-59522-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-12/txt/msg01344.txt.bz2 Content-length: 637 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY522 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |mpolacek at gcc dot gnu.org Resolution|--- |INVALID --- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Bugzilla isn't the right place for these kind of questions, use gcc-help mailing list. FWIW, I don't see why it shouldn't work with g++.
next prev parent reply other threads:[~2013-12-16 8:48 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 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 [this message] 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-pqdoDKxyLb@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: linkBe 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).