public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/64425] [5 Regression] r219076 causes 36% tramp3d slowdown Date: Sun, 04 Jan 2015 16:51:00 -0000 [thread overview] Message-ID: <bug-64425-4-DKWA5bdjcP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64425-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64425 --- Comment #4 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- I've tested the patch, too. There were two issues. 1) on ppc64: (after training) trippels@gcc2-power8 ~ % ~/gcc_test/usr/local/bin/g++ -Ofast -fprofile-use -w tramp3d-v4.cpp tramp3d-v4.cpp:64206:1: internal compiler error: in edge_badness, at ipa-inline.c:1030 } ^ 0x110330ff edge_badness ../../gcc/gcc/ipa-inline.c:1030 0x11039083 update_edge_key ../../gcc/gcc/ipa-inline.c:1059 0x11039083 inline_small_functions ../../gcc/gcc/ipa-inline.c:1634 0x1103b0af ipa_inline ../../gcc/gcc/ipa-inline.c:2175 0x1103b0af execute ../../gcc/gcc/ipa-inline.c:2548 Please submit a full bug report, with preprocessed source if appropriate. 2) Firefox PGO/LTO build on x86_64 segfaults on start.
next prev parent reply other threads:[~2015-01-04 16:51 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-28 9:30 [Bug ipa/64425] New: " trippels at gcc dot gnu.org 2014-12-28 9:38 ` [Bug ipa/64425] " trippels at gcc dot gnu.org 2014-12-28 19:02 ` hjl.tools at gmail dot com 2015-01-04 16:37 ` hubicka at gcc dot gnu.org 2015-01-04 16:51 ` trippels at gcc dot gnu.org [this message] 2015-01-12 9:28 ` hubicka at gcc dot gnu.org 2015-01-12 10:18 ` 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-64425-4-DKWA5bdjcP@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).