From: Matt <matt@use.net>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: bootstrap comparison failure with bootstrap-lto
Date: Wed, 16 Nov 2011 21:55:00 -0000 [thread overview]
Message-ID: <Pine.NEB.4.64.1111161146560.4352@cesium.clock.org> (raw)
In-Reply-To: <mcrsjlq7399.fsf@dhcp-172-18-216-180.mtv.corp.google.com>
On Mon, 14 Nov 2011, Ian Lance Taylor wrote:
> Matt <matt@use.net> writes:
>
>> I am getting this on Ubuntu 11.10/amd64. If I remove the
>> --with-build-config=bootstrap-lto, the build succeeds just fine. Is
>> this a known problem, or should I file a bug? (A search of bugzilla
>> didn't bring up this specific symptom.)
>
>> libcpp/lex.o differs
>
> What are the differences between stage2-libcpp/lex.o and
> stage3-libcpp/lex.o? Ignore the fact that one will have debug info and
> the other will not. Look at the readelf -S output for both files, and
> see if there are any differences in sections whose names do not start
> with ".debug".
in stage2-libcpp/lex.o:
[79] .init_array INIT_ARRAY 0000000000000000 00021280
0000000000000008 0000000000000000 WA 0 0 8
[80] .rela.init_array RELA 0000000000000000 0003a8e8
0000000000000018 0000000000000018 101 79 8
in stage3-libcpp/lex.o:
[79] .ctors PROGBITS 0000000000000000 00021280
0000000000000008 0000000000000000 WA 0 0 8
[80] .rela.ctors RELA 0000000000000000 0003a8e0
0000000000000018 0000000000000018 101 79 8
There's a few other minor differences, but they're related to debug stuff,
as far as I can tell.
> Also, what linker are you using?
ld --version outputs:
GNU ld (GNU Binutils for Ubuntu) 2.21.53.20110810
AFAIK, I'm using the default linker for Ubuntu 11.10/amd64.
--
tangled strands of DNA explain the way that I behave.
http://www.clock.org/~matt
next prev parent reply other threads:[~2011-11-16 19:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 22:23 Matt
2011-11-15 5:56 ` Ian Lance Taylor
2011-11-16 21:55 ` Matt [this message]
2011-11-17 5:43 ` Ian Lance Taylor
2011-11-18 6:35 ` Matt
2011-11-18 13:47 ` Ian Lance Taylor
2011-11-18 21:08 ` Matt
2011-11-19 1:11 ` Ian Lance Taylor
2011-11-19 2:41 ` Matt
2011-11-19 15:37 ` Ian Lance Taylor
2011-11-20 6:51 ` Matt
2011-11-20 7:32 ` Ian Lance Taylor
2011-11-20 20:23 ` Matt Hargett
2011-11-21 17:27 ` Ian Lance Taylor
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=Pine.NEB.4.64.1111161146560.4352@cesium.clock.org \
--to=matt@use.net \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
/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).