Re: to reduce footprint

[Kristof Provost]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> Thanks Michael! Sorry for any confusions. What I concern is not memory 
> footprint, but the physical size of the binary. Yes, I am developing embedded 
> applications. I am wondering some general ideas of how to make the footprint 
> smaller for physical files? Any ideas or comments?
> 
> 
> regards,
> George
> 
> ----- Original Message ----
> From: Michael Eager <address@hidden>
> To: Lin George <address@hidden>
> Sent: Friday, December 22, 2006 1:21:47 AM
> Subject: Re: to reduce footprint
> 
> 
> Lin George wrote:
>> Thanks Michael! I am interested why using printf will make footprint/malloc 
>> will make footprint larger? I think they are just some functions from other 
>> shared libraries, which will only have a link/address in the module which 
>> invokes them -- they are not inline functions. Why using printf and malloc 
>> will make footprint larger?
> 
> I'm not sure why you sent this to the make help list.
> Try address@hidden
> 
> You've never said what your target is or how you are
> building your application.  It's hard to guess what
> you are doing.
> 
> Most folks concerned about memory footprint are working
> on embedded systems with statically linked applications.
> Most folks who have systems which have shared libraries
> don't have large concerns about memory footprint.
> 

As a rough guide:
 - Strip debug information (strip)
 - Optimize for size (-Os)
 - Use gcc's -fdata-sections/-ffunction-sections and ld's -gc-sections
to remove unused functions.
 - use a compressed file system like SquashFS. (depending on your target
and requirements of course)

Kristof


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFis67UEZ9DhGwDugRA0A7AKCetYRIo3qSVSBrP2CoJEblo9vMjwCfU70n
yKKYGotnz1WmXus8P7U+1sY=
=uscv
-----END PGP SIGNATURE-----