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: Lawrence Gold <email@hidden>
- Date: Tue, 9 Aug 2005 10:50:47 -0600
On Aug 9, 2005, at 8:09 AM, Stefan Werner wrote:
Hi,
I'm ported a large project from CodeWarrior to Xcode (using gcc3.3)
and linking a debug build now takes 19 minutes on my PowerBook (G4
1.5GHz, 1.25GB RAM). A quick glance at top tells me that RAM is the
bottleneck, the ld process goes up to a VSIZE of 2.31GB, there's
lots of pageins/pageouts and the CPU idles at 70%. The resulting
binary is 300MB in size, 200MB if I enable dead code stripping (for
comparison, CodeWarrior links in one minute, less than 500MB VSIZE
and producing a binary of 25MB, .xSYM and .xMAP being 30MB combined).
Are there any tricks to bring my linking times down to reasonable
sizes, other than trading my PowerBook for a G5 with 4GB RAM?
Zerolink refuses cooperation, when I turn it on, ld complains about
not being able to find my static libraries.
If your "Level of Debug Symbols" setting is "All Symbols [full, -
gfull]", switch it to "Default [default -g]". This should make a
dramatic difference with GCC 3.3, though the link time will still be
longer than CodeWarrior's.
_______________________________________________
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