X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-1.5 required=5.0	tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Message-ID: <4C7D0F3F.4050700@sidefx.com>
Date: Tue, 31 Aug 2010 10:18:39 -0400
From: Edward Lam <edward@sidefx.com>
User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:2.0b5pre) Gecko/20100820 Shredder/3.2a1pre
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Cygwin slow on x64 systems
References: <4C7CA209.60603@onevision.de> <20100831140842.GA11833@ednor.casa.cgf.cx>
In-Reply-To: <20100831140842.GA11833@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On 8/31/2010 10:08 AM, Christopher Faylor wrote:
>
> Here's what I'm saying:  It makes absolutely no sense that moving the
> call would have any effect.  The code is the way it is for a reason
> so we're not going to just revert the change.

I don't think anyone is asking to revert the change.

In any case, is it absolutely necessary for us to call 
wait_for_sigthread() before we do the other initialization in 
dll_crt0_1() ? ie. can we move it further down? Or perhaps we can 
reorder the initialization code somewhat such that we can do more work 
before calling wait_for_sigthread()?

Regards,
-Edward

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple