RE: crosstool bloat

["Dave Korn" <dave dot korn at artimi dot com>]

----Original Message----
>From: David Karlton
>Sent: 18 September 2005 22:24

>  The build seems
> to work, but when I compile anything with the resulting compiler, all my
> output files are suddenly quite huge -- anything that would have
> compiled very small with 0.28 (eg. a 5k binary under 0.28) is now right
> around 68k, consistently, with 0.38.  I simply ran "sh ./demo-mipsel.sh"
> after editing the script to create the desired build.
> 
> Any idea what may be causing the executables to be so large?

  Lots of things *could* cause it, all the way down the toolchain starting
at the compiler and ending with the linker.

>  I can't
> recall what I had done in the installation for 0.28 to make the binaries
> be "normal".  Is there an easy way to figure out what is getting
> included into my builds?

  Yep, it's called objdump.  Compile a 'hello world' program with the old
and new compiler, and see what's different.

  My first guess would be that the new compiler is linking statically
against large chunks of glibc when the old one was linking against a shared
glibc.  Maybe a '--enable-shared' got left out of configure options
somewhere?


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com