Re: dead-code stripping, is it possible?
Re: dead-code stripping, is it possible?
- Subject: Re: dead-code stripping, is it possible?
- From: Markus Hitter <email@hidden>
- Date: Tue, 1 Jun 2004 23:37:46 +0200
Am 01.06.2004 um 18:24 schrieb Kevin Hoyt:
Now let's say that I don't care if other applications fail if they
attempt to link against my statically linked binary...
"Other applications" means your own application as well as soon as you
have more than one huge binary.
Is it possible to have the linker strip dead code? Is there an option
to
enable this?
Usually, there isn't any dead code to strip.
All those frameworks you link against already exist somewhere and don't
take up additional disk space if you link against them.
For memory usage, those frameworks are mapped into memory, i.e. it's
loaded just what you need, rounded up to the next 4 KB boundary.
Same for bundles & dynamic libraries.
Exception are dead functions in your own sources and linking against
static libraries. Both take disk space but not neccessarily memory.
Yet you have the reason why static linking is kind of depreceated in OS
X and why none of the common binaries, not even the kernel ist
statically linked.
This is how I understand things.
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.