Testing GCC on Cygwin made substantially easier [was Re: dragonegg in FSF gcc?]

[Dave Korn]

On 13/04/2010 17:57, Paolo Bonzini wrote:

> The fact that testing under Cygwin is so much slower certainly has an
> impact.  

  It gets more manageable at -j levels, but there's an underlying bug in the
Cygwin DLL's process info management that causes expect to fall into
cpu-spinning lockups and cascading process fork collapse syndrome.

  Until I find time to do a more major rewrite, anyone who wants to do testing
on Cygwin could do worse than apply the sticking-plaster patch that I posted at:

  http://www.mail-archive.com/cygwin-patches@cygwin.com/msg04677.html

and build themselves a locally modified version of the Cygwin DLL that will
happily run make check at significant -j levels (I think I tried 12 at most;
I've only got a dual-core cpu so it wasn't exactly efficient, but it proved
that the patch holds up under substantial load).

    cheers,
      DaveK