public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@nildram.co.uk>
To: Jakub Jelinek <jakub@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: Fix --gc-sections for C++ MIPS ELF
Date: Tue, 04 Dec 2007 10:08:00 -0000	[thread overview]
Message-ID: <87wsru3h8p.fsf@firetop.home> (raw)
In-Reply-To: <20071202220015.GA2947@sunsite.mff.cuni.cz> (Jakub Jelinek's 	message of "Sun\, 2 Dec 2007 23\:00\:15 +0100")

Jakub Jelinek <jakub@redhat.com> writes:
> On Sun, Dec 02, 2007 at 08:15:15PM +0000, Richard Sandiford wrote:
>> I tested the changes by running the C++ and libstdc++-v3 testsuites
>> on x86_64-linux-gnu and mipsisa64-elf with -Wl,--gc-sections.
>> The C++ PCH tests failed, but the results were otherwise identical
>> to those without -Wl,--gc-sections.  There were also no regressions
>> in the binutils, gas and ld testsuites for x86_64-linux-gnu,
>> mipsisa64-elf and mips64-linux-gnu.
>
> Another desirable test would be to build libgcj and glibc (as examples of
> really huge .eh_frame, including hand written .eh_frame, gas generated
> .cfi_* stuff and gcc generated stuff) on x86_64-linux, i686-linux, ppc-linux
> at least and comparing the resulting .eh_frame between unpatched and patched
> ld.

OK.  I don't have access to ppc-linux, but I tried it on the other two.
Specifically, with and without the patches, I:

  - built binutils from scratch and installed it into fixed location 1
  - ran a full gcc bootstrap and regression test from fixed location 2
    and installed into fixed location 3.  I did this with fixed location 1
    at the head of the path, and with --with-{as,ld} pointing at the
    assembler and linker in fixed location 1.
  - built glibc with fixed location 1 and fixed location 3 at the head
    of the path.
  - moved fixed location 3 and the glibc build directory away for later
    comparison.

I double-checked that the right binutils and gccs were being used
in each step.

The two libc.sos were identical.  The libgcj.sos differed only in
debugging information, due to things like different random seeds;
the stripped versions were also identical.  FWIW, libstdc++-v3
(which is built with -Wl,--gc-sections) stayed the same too.

The gcc regression-test results were also the same for both builds.
I extended the -Wl,--gc-sections testing on i686-pc-linux-gnu
(adding to the original x86_64-linux-gnu and mipsisa64-elf).

The patched binutils included the eighth patch that I just posted.

Richard

  reply	other threads:[~2007-12-04 10:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-02 20:15 Richard Sandiford
2007-12-02 20:18 ` [PATCH 1/7] " Richard Sandiford
2007-12-02 20:19 ` [PATCH 2/7] " Richard Sandiford
2007-12-02 20:28 ` [PATCH 3/7] " Richard Sandiford
2007-12-02 20:31 ` [PATCH 4/7] " Richard Sandiford
2007-12-02 20:35 ` [PATCH 5/7] " Richard Sandiford
2007-12-02 20:37 ` [PATCH 6/7] " Richard Sandiford
2007-12-02 20:39 ` [PATCH 7/7] " Richard Sandiford
2007-12-02 21:55 ` Jakub Jelinek
2007-12-04 10:08   ` Richard Sandiford [this message]
2007-12-02 22:26 ` Eric Botcazou
2007-12-04 10:02   ` [PATCH 8/7] " Richard Sandiford
2007-12-04 11:39     ` Eric Botcazou
2007-12-15  1:46 ` Alan Modra
2007-12-15  9:46   ` Richard Sandiford

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=87wsru3h8p.fsf@firetop.home \
    --to=rsandifo@nildram.co.uk \
    --cc=binutils@sourceware.org \
    --cc=jakub@redhat.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).