This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Fw: gcc 3.2 code bloating?
- From: Eljay Love-Jensen <eljay at adobe dot com>
- To: Miguel Ramírez <mramirez at iua dot upf dot es>, "Rupert Wood" <rup at kanat dot pair dot com>
- Cc: <gcc-help at gcc dot gnu dot org>
- Date: Wed, 09 Oct 2002 07:27:20 -0500
- Subject: Re: Fw: gcc 3.2 code bloating?
- References: <Pine.BSF.4.44.0210090458530.56830-100000@kanat.pair.com>
Hi Miguel,
On the various platforms, check out the dependencies of the executable.
On Unix-ish systems:
ldd helloworld
I don't know how to do the equivalent thing on Windows / Cygwin's Bash for
Windows / MinGW type of environment.
I'm guessing that the larger executable is statically linking in a lot of
infrastructure, whereas the smaller executables are dynamically linking in
a lot of infrastructure -- and thus give the appearance of smaller
executables, but the actual in-memory footprints would be
comparable. (Ignoring the potential benefit of multiple processes sharing
a single code instance of a dynamically loaded library.)
I'm betting that will solve the mystery. Or uncover new mysteries.
Sincerely,
--Eljay