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] New: [4.8 Regression] Benchmarks in SPEC CPU 2006 failed to build
Date: Tue, 24 Apr 2012 21:49:00 -0000	[thread overview]
Message-ID: <bug-53106-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53106

             Bug #: 53106
           Summary: [4.8 Regression] Benchmarks in SPEC CPU 2006 failed to
                    build
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: hjl.tools@gmail.com
                CC: areg.melikadamyan@gmail.com, hubicka@gcc.gnu.org


On Linux/x86-64 and Linux/ia32, revision 186700:

http://gcc.gnu.org/ml/gcc-cvs/2012-04/msg00652.html

caused 2 benchmarks in SPEC CPU 2006 failed to build.

483.xalancbmk on Linux/x86-64:

g++ -c -o UnionDatatypeValidator.o -DSPEC_CPU -DNDEBUG  -DAPP_NO_THREADS
-DXALAN_INMEM_MSG_LOADER -I. -Ixercesc -Ixercesc/dom -Ixercesc/dom/impl
-Ixercesc/sax -Ixercesc/util/MsgLoaders/InMemory
-Ixercesc/util/Transcoders/Iconv -Ixalanc/include -DPROJ_XMLPARSER
-DPROJ_XMLUTIL -DPROJ_PARSERS -DPROJ_SAX4C -DPROJ_SAX2 -DPROJ_DOM
-DPROJ_VALIDATORS -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER -O3
-funroll-loops -ffast-math    -DSPEC_CPU_LP64  -DSPEC_CPU_LINUX    
UnionDatatypeValidator.cpp
...
UnionDatatypeValidator.cpp:605:1: error: caller edge frequency 3624 does not
match BB frequency 334
 XERCES_CPP_NAMESPACE_END
 ^
_ZN11xercesc_2_59XMLString6equalsEPKtS2_.part.2/2066 (static bool
xercesc_2_5::XMLString::_ZN11xercesc_2_59XMLString6equalsEPKtS2_.part.2(const
XMLCh*)) @0x2aaaaba46888
  Type: function
  Visibility: prevailing_def_ironly artificial
  References: 
  Referring: 
  Function static bool
xercesc_2_5::XMLString::_ZN11xercesc_2_59XMLString6equalsEPKtS2_.part.2(const
XMLCh*)/2066 is inline copy in static bool xercesc_2_5::XMLString::equals(const
XMLCh*, const XMLCh*)/179
  Availability: local
  Function flags: analyzed body local finalized
  Called by: _ZN11xercesc_2_59XMLString6equalsEPKtS2_/179 (3.62 per call)
(inlined) 
  Calls: 
UnionDatatypeValidator.cpp:605:1: internal compiler error: verify_cgraph_node
failed
 XERCES_CPP_NAMESPACE_END
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.


             reply	other threads:[~2012-04-24 21:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 21:49 hjl.tools at gmail dot com [this message]
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
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@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).