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/51974] New: GCC fails to bootstrap with --enable-checking=release on opensuse
Date: Mon, 23 Jan 2012 19:56:00 -0000 [thread overview]
Message-ID: <bug-51974-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51974
Bug #: 51974
Summary: GCC fails to bootstrap with --enable-checking=release
on opensuse
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
Host: Opensuse 12.1 x86_64
Target: x86_64-unknown-linux-gnu
I tried to build the latest trunk (183442) with --enable-checking=release on
the Opensuse 12.1 x86_64 host. Checking between stage2 and stage3 fails.
Bootstrap comparison failure!
gcc/tree-ssa-dom.o differs
gcc/tree-ssa-structalias.o differs
gcc/final.o differs
gcc/combine.o differs
gcc/reload1.o differs
gcc/tree-ssa-ccp.o differs
gcc/tree-ssa.o differs
This version passes on Fedora Core 15 x86_64. Anyone seen this? I am seeing the
following differences:
reload1.o:stage2
30b4: 0f 1f 40 00 nopl 0x0(%rax)
30b8: 41 8b 57 08 mov 0x8(%r15),%edx
30bc: 83 c2 7d add $0x7d,%edx
30bf: e9 7c fe ff ff jmpq 2f40
<_ZL16free_for_value_pi12machine_modei11reload_typeP7rtx_defS2_ii+0x1c0>
b0d4: 0f 1f 40 00 nopl 0x0(%rax)
b0d8: 48 63 f6 movslq %esi,%rsi
b0db: 48 29 70 18 sub %rsi,0x18(%rax)
b0df: e9 3c fe ff ff jmpq af20
<_ZL19elimination_effectsP7rtx_def12machine_mode+0xe0>
reload1.o:stage3
30c8: 41 8b 57 08 mov 0x8(%r15),%edx
30cc: 83 c2 7d add $0x7d,%edx
30cf: e9 7c fe ff ff jmpq 2f50
<_ZL16free_for_value_pi12machine_modei11reload_typeP7rtx_defS2_ii+0x1c0>
30d4: 0f 1f 40 00 nopl 0x0(%rax)
b0e8: 48 63 f6 movslq %esi,%rsi
b0eb: 48 29 70 18 sub %rsi,0x18(%rax)
b0ef: e9 3c fe ff ff jmpq af30
<_ZL19elimination_effectsP7rtx_def12machine_mode+0xe0>
b0f4: 0f 1f 40 00 nopl 0x0(%rax)
next reply other threads:[~2012-01-23 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 19:56 nenad at intrepid dot com [this message]
2012-01-24 2:46 ` [Bug target/51974] [4.7 Regression] " pinskia at gcc dot gnu.org
2012-01-25 22:21 ` jakub at gcc dot gnu.org
2012-01-26 15:52 ` rguenth at gcc dot gnu.org
2012-01-30 23:03 ` jakub at gcc dot gnu.org
2012-01-31 8:11 ` nenad at intrepid dot com
2012-01-31 10:07 ` jakub at gcc dot gnu.org
2012-01-31 10:11 ` jakub at gcc dot gnu.org
2012-01-31 10:49 ` jakub 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-51974-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).