public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/53106] [4.8 Regression] Benchmarks in SPEC CPU 2006 failed to build Date: Tue, 24 Apr 2012 23:13:00 -0000 [thread overview] Message-ID: <bug-53106-4-u6l7TMDTes@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53106-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53106 --- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> 2012-04-24 23:12:19 UTC --- [hjl@gnu-35 delta]$ /export/gnu/import/git/gcc-test-spec/usr/bin/gcc -mx32 -O3 -S testcase.cc testcase.cc:31:35: error: caller edge frequency 3943 does not match BB frequency 390 template class FE_RaviartThomas<3>; ^ _ZNSt14_Bit_referenceaSEb.part.2/256 (std::_Bit_reference& std::_Bit_reference::_ZNSt14_Bit_referenceaSEb.part.2()) @0x7ffff112ed68 Type: function Visibility: prevailing_def_ironly visibility_specified artificial References: Referring: Function std::_Bit_reference& std::_Bit_reference::_ZNSt14_Bit_referenceaSEb.part.2()/256 is inline copy in std::_Bit_reference& std::_Bit_reference::operator=(bool)/26 Availability: local Function flags: analyzed body local finalized Called by: _ZNSt14_Bit_referenceaSEb/26 (3.94 per call) (inlined) Calls: testcase.cc:31:35: internal compiler error: verify_cgraph_node failed template class FE_RaviartThomas<3>; ^ Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. [hjl@gnu-35 delta]$ /export/gnu/import/git/gcc-test-spec/usr/bin/gcc -m32 -O3 -S testcase.cc testcase.cc:31:35: error: caller edge frequency 3943 does not match BB frequency 390 template class FE_RaviartThomas<3>; ^ _ZNSt14_Bit_referenceaSEb.part.2/256 (std::_Bit_reference& std::_Bit_reference::_ZNSt14_Bit_referenceaSEb.part.2()) @0x7ffff112ed68 Type: function Visibility: prevailing_def_ironly visibility_specified artificial References: Referring: Function std::_Bit_reference& std::_Bit_reference::_ZNSt14_Bit_referenceaSEb.part.2()/256 is inline copy in std::_Bit_reference& std::_Bit_reference::operator=(bool)/26 Availability: local Function flags: analyzed body local finalized Called by: _ZNSt14_Bit_referenceaSEb/26 (3.94 per call) (inlined) Calls: testcase.cc:31:35: internal compiler error: verify_cgraph_node failed template class FE_RaviartThomas<3>; ^ Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. [hjl@gnu-35 delta]$
next prev parent reply other threads:[~2012-04-24 23:13 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-24 21:49 [Bug middle-end/53106] New: " hjl.tools at gmail dot com 2012-04-24 21:50 ` [Bug middle-end/53106] " hjl.tools at gmail dot com 2012-04-24 23:13 ` hjl.tools at gmail dot com [this message] 2012-04-24 23:13 ` hjl.tools at gmail dot com 2012-04-25 11:05 ` rguenth at gcc dot gnu.org 2012-04-25 14:35 ` hubicka at gcc dot gnu.org 2012-04-25 14:39 ` hjl.tools at gmail dot com 2012-04-25 16:12 ` hubicka at gcc dot gnu.org 2012-04-25 16:22 ` hubicka at gcc dot gnu.org 2012-05-03 15:17 ` wschmidt at gcc dot gnu.org 2012-05-03 19:19 ` hubicka at gcc dot gnu.org 2012-09-07 11:28 ` rguenth 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-53106-4-u6l7TMDTes@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).