where are the files ld is working on?
This seems eerily like a situation here where using PVCS on files located
on a samba server take forever (sometimes). During that time no other
task can access the affected drive. Even "ls" will block until the action
completes. No extraordinary cpu load occurs. The same action when the
files are local completes quickly, as expected.
Roger Wells, P.E.
221 Third St
Newport, RI 02840
Jeff Williams <jwilliams@...>
Sent by: mingw-users-admin@...
12/03/2003 10:35 PM
Please respond to mingw-users
Subject: [Mingw-users] re: not a toy (ld slow)
> From: "Miroslav Fidler" <cxl@...>
> To: <mingw-users@...>
> Subject: Re: [Mingw-users] Re: not a toy
> Date: Wed, 3 Dec 2003 14:50:35 +0100
> Anyway, I definitely WAS succesful changing our GCC build process so
> that it compiles a whole bunch of files in single go - and it resulted
> real 4 times speedup in large rebuilds. It is still not as fast as MSC
> MSC can use the same technology too, giving it another 25% advantage.
> Anyway, total compile time dropped from 45 minutes to about 12 minutes,
> which is something I can live with. (MSC dropped from 4 minutes to 3).
> If only LD was somewhat better/faster... Out of that 12 minutes, 2
> minutes are linking - which unfortunately means that any rebuild, not
> complete, will be at least 2 minutes. But perhaps the solution is to use
> .dlls for group of related files for debug builds, even if I plan to
> release executable as single .exe.
I've noticed that ld seems to spend a tremendous amount of time
not using any CPU at all which leads me to conclude it is waiting on
Has anyone else notice this? Sometimes it might take 2 minutes to
link my project in debug mode. When I bring up the task manager
LD will sometimes go for 10 seconds at a time without using any
CPU at all.
Other times, when ld is running, if I try to open up a file in
a text editor, by right clicking and choosing open with...
nothing will happen and explorer locks up. Then the very instant
ld completes my file opens in the editor. and this happens
even when I try to open a file 100% totally unrelated to the cpp
code. (i.e. c\foo.txt)
Anyways maybe this is something better suited as a bug report, but
just curious if anyone else experience this.
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
MinGW-users mailing list
You may change your MinGW Account Options or unsubscribe at: