Marcin Dalecki wrote:
Wiadomość napisana w dniu 2007-01-24, o godz23:52, przez Mike Stump:
On Jan 24, 2007, at 1:12 PM, Marcin Dalecki wrote:
It could be a starting point to help avoiding quite a lot of
overhead needed to iterate over command line options for example.
Odd. You think that time is being spent iterating over the command
line options?
No I think plenty of time goes to dejagnu churning and iterative
restarts of new gcc process instances as well as other system calls.
That's at least what a casual look at a top and the sluggishness of
the disk system I'm using suggests. The option churning I did have in
mind was like
gcc -O0 test.c, gcc -01 test.c, gcc -O2 test.c
runs in sequence, which are quite common.
This is certainly true on Cygwin, where a "make check-fortran" takes on
the order of a dozen hours, rather than three under Linux on the same
computer within a VMWare session. That's just circumstantial evidence
for what's going on on Linux, but it seems pretty strong circumstantial
evidence to me.
(Also, when I'm running a GCC test run, even under Linux, my drives get
hot. I think that's probably relevant data too.)
- Brooks
