This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 4.6.0 Released
- From: Richard Henderson <rth at redhat dot com>
- To: Dave Korn <dave dot korn dot cygwin at gmail dot com>
- Cc: Bernd Roesch <nospamname at gmx dot de>, Joe Buck <Joe dot Buck at synopsys dot COM>, FX <fxcoudert at gmail dot com>, Kai Tietz <ktietz70 at googlemail dot com>, "piotr dot wyderski at gmail dot com" <piotr dot wyderski at gmail dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- Date: Tue, 29 Mar 2011 14:01:26 -0700
- Subject: Re: GCC 4.6.0 Released
- References: <yam12140.2795.283802416@mail.gmx.net> <4D91D660.7050505@gmail.com>
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~