Re: reducing ld's memory footprint (19 minutes of linking)
Re: reducing ld's memory footprint (19 minutes of linking)
- Subject: Re: reducing ld's memory footprint (19 minutes of linking)
- From: Dair Grant <email@hidden>
- Date: Tue, 9 Aug 2005 19:06:22 +0100
Lawrence Gold wrote:
>Do you have Dead Code Stripping enabled? If so, disabling it should
>allow you to debug successfully with the default debug symbols. Our
>projects are set to the default, and I haven't had any problems with
>missing variables.
We have also been round this loop (dual-G5 with 1.25Gb of memory swaps
for minutes at a time, UI stops responding, and the final libraries are
hundreds of Mbs vs 10s of Mbs), and also tracked it down to -gfull.
We enabled this option purely because we want dead-code stripping, and
the docs say:
"You must also compile the object files with the -gfull option
to ensure that the resulting binaries can be properly debugged."
Since setting it to -gused, our link times are much more sensible. So
far we haven't noticed any problems with things going missing while
debugging, even with dead code stripping turned on.
Aside from the debugging requirement, the docs also say that:
"Although the -gfull option does create larger .o files, it often
leads to smaller executable files, even without dead-code
stripping enabled."
We haven't found that to be the case - the final binary, once stripped
of debug symbols, is the same size at all three levels. This is all C++,
with some basic STL usage but fairly straightforward.
-dair
___________________________________________________
mailto:email@hidden http://www.zonic.co.uk/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden