linux-gcc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* gcc cross mips output sizes too big
@ 2004-11-12 22:51 David Wuertele
  2004-12-15 12:15 ` Repost: " David Wuertele
  0 siblings, 1 reply; 2+ messages in thread
From: David Wuertele @ 2004-11-12 22:51 UTC (permalink / raw)
  To: linux-gcc

I've been using crosstool-generated gcc-3.3.3 to build my mipsel
targets, and I find that the file sizes are humungous.  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


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Repost: gcc cross mips output sizes too big
  2004-11-12 22:51 gcc cross mips output sizes too big David Wuertele
@ 2004-12-15 12:15 ` David Wuertele
  0 siblings, 0 replies; 2+ messages in thread
From: David Wuertele @ 2004-12-15 12:15 UTC (permalink / raw)
  To: linux-gcc

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-12-15 12:15 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-11-12 22:51 gcc cross mips output sizes too big David Wuertele
2004-12-15 12:15 ` Repost: " David Wuertele

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 NNTP newsgroup(s).