Yes. AFAICT, it's intra .exp concurrency that's causing this.
Now that I think of it, maybe the problem is that file foo_0.c is
going to one job and foo_1.c is going to another?
Diego.
Cheers,
--
Rafael Avila de Espindola
Google | Gordon House | Barrow Street | Dublin 4 | Ireland
I've noticed some spurious failures in the lto tests (g++.dg/lto and
gcc.dg/lto). They only occur with -jN. The symptom is an error
message from ld complaining that a .lto.ltrans.o file is missing. I
think this is a bug in the lto.exp script because the tests work fine
with -j1.
I'll be taking
I've noticed some spurious failures in the lto tests (g++.dg/lto and
gcc.dg/lto). They only occur with -jN. The symptom is an error
message from ld complaining that a .lto.ltrans.o file is missing. I
think this is a bug in the lto.exp script because the tests work fine
with -j1.
I assume
On Wed, Nov 19, 2008 at 17:51, Ben Elliston [EMAIL PROTECTED] wrote:
I assume you mean when running make -jN check-gcc? Concurrency between
various .exp scripts should not cause you any problems, as each make
check is run in its own testsuite directory.
Yes. AFAICT, it's intra .exp
