public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kai Ruottu <karuottu@mbnet.fi>
To: karuottu@mbnet.fi
Cc: Frank Beesley <frank.beesley@aeroflex.com>,  gcc-help@gcc.gnu.org
Subject: Re: Updating powerpc-crosscompile environment from gcc-2.95.3
Date: Thu, 10 Nov 2005 10:16:00 -0000	[thread overview]
Message-ID: <43731F9C.9080206@mbnet.fi> (raw)
In-Reply-To: <4373136B.2070603@mbnet.fi>

Kai Ruottu wrote:

> If one has "some suitable" target C library,
> the '--enable-shared --enable-threads' can be used, otherwise both
> must be disabled and the result is a stripped GCC which maybe can
> or can not compile the C library ok. One cannot be sure about this
> without very deep understanding about the C library doings...

  I forgot to tell that the glibc-2.3.5 made with the stripped GCC
and the glibc-2.3.5 made with the complete GCC were different in
their library sizes, for instance the 'libc-2.3.5.so' was 1329938
bytes when produced with the stripped GCC but 1293873 bytes when
produced with the complete GCC. The SuSE 10.0/ppc one was 1510896
bytes for their glibc-2.3.5-40 (the 32-bit library). Whether
gcc-3.4.4 produces smaller code than gcc-4.0.2 (used in SuSE) or
then there are other big changes in their own glibc-2.3.5...

  Comparing those sizes is almost everything one could do simply,
but tools like 'nm' and 'objdump' could allow one to investigate
the differences more deeply...

  parent reply	other threads:[~2005-11-10 10:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-09 20:08 Frank Beesley
2005-11-09 21:22 ` Kai Ruottu
2005-11-09 21:33   ` corey taylor
2005-11-09 22:17     ` Kai Ruottu
2005-11-09 22:24     ` Kai Ruottu
2005-11-09 22:18   ` Frank Beesley
2005-11-10  9:24     ` Kai Ruottu
2005-11-10  9:58       ` Kai Ruottu
2005-11-10 10:16       ` Kai Ruottu [this message]
2005-11-10 17:02 ` Frank Beesley
  -- strict thread matches above, loose matches on Subject: below --
2005-11-05 13:53 Kimmo Mustonen

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=43731F9C.9080206@mbnet.fi \
    --to=karuottu@mbnet.fi \
    --cc=frank.beesley@aeroflex.com \
    --cc=gcc-help@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).