All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Wuertele <dave-gnus@bfnet.com>
To: linux-gcc@vger.kernel.org
Subject: Repost: gcc cross mips output sizes too big
Date: Wed, 15 Dec 2004 04:15:54 -0800	[thread overview]
Message-ID: <m3ekhrg3k5.fsf@bfnet.com> (raw)
In-Reply-To: m37joqznoj.fsf@bfnet.com

It's been a month and I still haven't found any answers.  Anyone here
know why object files have grown significantly since 2.95.3?

I've been using crosstool-generated gcc-3.3.3 to build my mipsel
targets, and I find that the file sizes are ginormous.  After
stripping the objects, I get file sizes that are up to TWICE as large
as similarly generated gcc-2.96 code.  Do these sizes not look out of
line?

   bytes          gcc-3.3.3 generated files
  -------       --------------------------------
  1884160	/lib/libc-2.3.2.so
  1257472	/lib/libstdc++.so.5.0.5
  1048576	/usr/local/lib/libfreetype.so.1314.0.0.10
  1036288	/bin/busybox
  1011712	/bin/bash

   bytes          gcc-2.96 generated files
  -------       --------------------------------
  1531904	/lib/libc-2.2.4.so
  532480	/lib/libstdc++-3-libc6.2-2-2.10.0.so
  495616	/usr/local/lib/libfreetype.so.1314.0.0.10
  462848	/bin/busybox
  847872	/bin/bash

Compiling with -Os helps, but doesn't get close to the file sizes I
saw with my older cross-compiler.  It seems strange to me that moving
to a newer compiler will reduce the number of programs I can ship in
my little NAND flash.

Is there some way to generate a more efficient cross-compiler?

Thanks,
Dave


      reply	other threads:[~2004-12-15 12:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12 22:51 gcc cross mips output sizes too big David Wuertele
2004-12-15 12:15 ` David Wuertele [this message]

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=m3ekhrg3k5.fsf@bfnet.com \
    --to=dave-gnus@bfnet.com \
    --cc=linux-gcc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.