public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kirill.yukhin at intel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/50543] New: Bootstrap fails to build for latest 4.6.0 Date: Tue, 27 Sep 2011 14:41:00 -0000 [thread overview] Message-ID: <bug-50543-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50543 Bug #: 50543 Summary: Bootstrap fails to build for latest 4.6.0 Classification: Unclassified Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned@gcc.gnu.org ReportedBy: kirill.yukhin@intel.com Hi, I am not sure, but possibly this will duplicate some other bug. Bootstrap miscompares on latest 4.6.0 sources: $ ../gcc/configure i686-linux --with-arch=corei7 --with-cpu=corei7 --enable-clocale=gnu --with-system-zlib --enable-shared --with-demangler-in-ld --enable-cloog-backend=isl --with-fpmath=sse --prefix=$PREFIX --enable-languages=c,c++,fortran $ make -j24 ... make[2]: Entering directory `/export/users/kyukhin/ws_ref/4.6_build' make[3]: Entering directory `/export/users/kyukhin/ws_ref/4.6_build' rm -f stage_current make[3]: Leaving directory `/export/users/kyukhin/ws_ref/4.6_build' Comparing stages 2 and 3 warning: gcc/cc1plus-checksum.o differs warning: gcc/cc1-checksum.o differs Bootstrap comparison failure! gcc/tree-ssa-loop-im.o differs gcc/loop-iv.o differs gcc/ira-build.o differs gcc/reload.o differs gcc/gcov.o differs gcc/tree-vect-stmts.o differs gcc/tree-vrp.o differs gcc/reload1.o differs gcc/bb-reorder.o differs gcc/real.o differs gcc/ira.o differs gcc/dwarf2out.o differs gcc/tree-ssa-loop-prefetch.o differs gcc/fold-const.o differs gcc/ira-emit.o differs gcc/cfgexpand.o differs gcc/build/genautomata.o differs gcc/omega.o differs gcc/ira-conflicts.o differs gcc/gcc.o differs gcc/store-motion.o differs gcc/ipa-split.o differs gcc/sel-sched.o differs gcc/plugin.o differs gcc/tree-predcom.o differs gcc/driver-i386.o differs gcc/tree.o differs libcpp/directives.o differs libcpp/charset.o differs libcpp/traditional.o differs libcpp/expr.o differs libdecnumber/bid2dpd_dpd2bid.o differs libiberty/sha1.o differs libiberty/pic/sha1.o differs lto-plugin/.libs/lto-plugin.o differs make[2]: *** [compare] Error 1 make[2]: Leaving directory `/export/users/kyukhin/ws_ref/4.6_build' make[1]: *** [stage3-bubble] Error 2 make[1]: Leaving directory `/export/users/kyukhin/ws_ref/4.6_build' make: *** [all] Error 2
next reply other threads:[~2011-09-27 14:29 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-27 14:41 kirill.yukhin at intel dot com [this message] 2011-09-27 14:47 ` [Bug bootstrap/50543] " redi at gcc dot gnu.org 2011-09-27 16:41 ` kirill.yukhin at intel dot com 2011-09-27 17:38 ` [Bug bootstrap/50543] Bootstrap fails to build for latest 4.6 hjl.tools at gmail dot com 2011-09-27 20:49 ` hjl.tools at gmail dot com 2011-09-28 8:22 ` kirill.yukhin at intel dot com 2011-09-28 15:38 ` evstupac at gmail dot com 2011-09-28 20:01 ` kirill.yukhin at intel dot com 2014-10-10 15:18 ` hjl.tools at gmail dot com
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-50543-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: 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).