public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nenad at intrepid dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/50709] New: stage3 bootstrap comparison fail on x86_64 with --disable-checking config option Date: Wed, 12 Oct 2011 22:29:00 -0000 [thread overview] Message-ID: <bug-50709-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50709 Bug #: 50709 Summary: stage3 bootstrap comparison fail on x86_64 with --disable-checking config option Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned@gcc.gnu.org ReportedBy: nenad@intrepid.com Target: x86_64 I was not able to build the latest GCC with --disable-checking specified. The following errors from stage3 comparison phase are reported: Bootstrap comparison failure! gcc/tree-ssa-reassoc.o differs gcc/ipa-inline-analysis.o differs gcc/sel-sched.o differs gcc/tree-ssa-ccp.o differs gcc/ipa-cp.o differs gcc/objc/objc-next-runtime-abi-02.o differs gcc/tree-stdarg.o differs gcc/fortran/dump-parse-tree.o differs gcc/tree-inline.o differs gcc/cfgexpand.o differs gcc/tree-data-ref.o differs gcc/ggc-page.o differs gcc/build/genautomata.o differs gcc/ipa-pure-const.o differs gcc/dwarf2out.o differs gcc/tree-vrp.o differs gcc/java/expr.o differs gcc/tree-ssa-ter.o differs gcc/sched-rgn.o differs gcc/haifa-sched.o differs gcc/tree-ssa-sccvn.o differs gcc/tree-loop-distribution.o differs gcc/tree-ssa-math-opts.o differs gcc/tree-ssa-structalias.o differs libiberty/pic/cp-demangle.o differs libiberty/cp-demangle.o differs make[2]: *** [compare] Error 1 After checking on one of the files (ggc-page.c) I see the following differences in the object file: stage2: _ZL10alloc_anonPcm.part.0: .LFB1675: .cfi_startproc pushq %rax .cfi_def_cfa_offset 16 movl $.LC0, %edi call perror movl $1, %edi call exit .cfi_endproc [...] call _ZL10alloc_anonPcm.part.0 stage3: [...] no procedure declared, and the this code is placed instead of the call statment in stage2 .loc 1 670 0 movl $.LC3, %edi call perror .LVL149: .loc 1 671 0 movl $1, %edi call exit By looking at the source code I think that the above comes form this source code. 656 static inline char * 657 alloc_anon (char *pref ATTRIBUTE_UNUSED, size_t size) 658 { [...] 668 if (page == (char *) MAP_FAILED) 669 { 670 perror ("virtual memory exhausted"); 671 exit (FATAL_EXIT_CODE); 672 } [...] 682 return page; 683 }
next reply other threads:[~2011-10-12 22:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-12 22:29 nenad at intrepid dot com [this message] 2011-10-13 9:29 ` [Bug bootstrap/50709] " rguenth at gcc dot gnu.org 2011-10-13 15:14 ` [Bug bootstrap/50709] stage3 bootstrap comparison failure " belyshev at depni dot sinp.msu.ru 2011-10-17 11:23 ` rguenth at gcc dot gnu.org 2011-10-17 18:14 ` [Bug bootstrap/50709] [4.7 Regression] " pinskia at gcc dot gnu.org 2011-10-17 18:37 ` nenad at intrepid dot com 2011-10-20 11:46 ` hubicka at gcc dot gnu.org 2011-10-21 2:23 ` gfunck at gcc dot gnu.org 2011-10-21 2:45 ` belyshev at depni dot sinp.msu.ru 2011-11-24 15:24 ` dnovillo 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-50709-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).