Fw: gcc 3.2 code bloating?

[Eljay Love-Jensen]

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