On 03/29/2011 05:53 AM, Dave Korn wrote: >> I think it can too in readme add that on current cygwin on win 64 and >> multicore CPU GCC compile lots slower as on single CPU systems. To speed up >> GCC and compile 3* faster in windows taskmanager can the CPU number set to >> 1 for the shell task. >> >> But i hope there come some day a fix for this problem.I get sometimes hang >> and after 10-20 sec come a message that vfork problem is detect. maybe when >> GCC use fork for task create or native windows task create it work better ? > > This sounds like the generic Cygwin fork-error/BLODA problem and not > specific to GCC.
Indeed. For what it's worth, gcc itself *does* use the Cygwin spawn* functions to avoid this problem, but (curiously) the Cygwin versions of make, bash, and expect do not. Therefore the problem can still be seen during a build. r~
