public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "htl10 at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/40894] [4.4/4.5/4.6/4.7 Regression] bootstrap4-lean failed crtfastmath.o comparision
Date: Sun, 01 May 2011 22:32:00 -0000 [thread overview]
Message-ID: <bug-40894-4-3aNUfmiHTV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40894-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40894
Hin-Tak Leung <htl10 at users dot sourceforge.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |4.4.6
--- Comment #9 from Hin-Tak Leung <htl10 at users dot sourceforge.net> 2011-05-01 22:27:42 UTC ---
4.4.6 failed at same place.
make[2]: Entering directory `/home/htl10/tmp-build/gcc-446-obj-2'
make[3]: Entering directory `/home/htl10/tmp-build/gcc-446-obj-2'
rm -f stage_current
make[3]: Leaving directory `/home/htl10/tmp-build/gcc-446-obj-2'
Comparing stages 3 and 4
Bootstrap comparison failure!
./crtfastmath.o differs
make[2]: *** [compare3] Error 1
make[2]: Leaving directory `/home/htl10/tmp-build/gcc-446-obj-2'
make[1]: *** [stage4-bubble] Error 2
make[1]: Leaving directory `/home/htl10/tmp-build/gcc-446-obj-2'
make: *** [bootstrap4-lean] Error 2
bash-2.05a# objdump -Dxzs stage3-gcc/crtfastmath.o > stage3-dump
bash-2.05a# objdump -Dxzs stage4-gcc/crtfastmath.o > stage4-dump
bash-2.05a# diff -u stage3-dump stage4-dump
--- stage3-dump 2011-05-01 23:14:28.000000000 +0100
+++ stage4-dump 2011-05-01 23:14:41.000000000 +0100
@@ -1,6 +1,6 @@
-stage3-gcc/crtfastmath.o: file format ecoff-littlealpha
-stage3-gcc/crtfastmath.o
+stage4-gcc/crtfastmath.o: file format ecoff-littlealpha
+stage4-gcc/crtfastmath.o
architecture: alpha, flags 0x00000035:
HAS_RELOC, HAS_LINENO, HAS_SYMS, HAS_LOCALS
start address 0x00000000
@@ -70,7 +70,7 @@
0010 00301f22 10807da7 00405b6b 0100ba27 .0."..}..@[k...'
0020 2480bd23 00005ea7 1000de23 0180fa6b $..#..^....#...k
Contents of section .xdata:
- 0030 31000000 02000204 00000000 00000000 1...............
+ 0030 01000000 02000204 00000000 00000000 ................
Contents of section .pdata:
0040 00000000 ecffffff ........
Contents of section .lita:
@@ -100,7 +100,7 @@
Disassembly of section .xdata:
00000030 <.xdata>:
- 30: 31 00 00 00 call_pal 0x31
+ 30: 01 00 00 00 call_pal 0x1
34: 02 00 02 04 .long 0x4020002
38: 00 00 00 00 halt
3c: 00 00 00 00 halt
bash-2.05a#
next prev parent reply other threads:[~2011-05-01 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-40894-4@http.gcc.gnu.org/bugzilla/>
2010-10-01 12:08 ` [Bug bootstrap/40894] [4.4/4.5/4.6 " jakub at gcc dot gnu.org
2010-12-15 5:17 ` htl10 at users dot sourceforge.net
2011-04-16 11:09 ` [Bug bootstrap/40894] [4.4/4.5/4.6/4.7 " jakub at gcc dot gnu.org
2011-05-01 22:32 ` htl10 at users dot sourceforge.net [this message]
2011-05-01 22:36 ` htl10 at users dot sourceforge.net
2011-08-05 1:27 ` htl10 at users dot sourceforge.net
2011-08-05 5:44 ` htl10 at users dot sourceforge.net
2012-09-10 16:08 ` htl10 at users dot sourceforge.net
2012-09-10 16:16 ` htl10 at users dot sourceforge.net
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-40894-4-3aNUfmiHTV@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).