X-Recipient: archive-cygwin AT delorie DOT 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: <4C7EA2CE.5000805@sidefx.com> Date: Wed, 01 Sep 2010 15:00:30 -0400 From: Edward Lam User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Cygwin slow on x64 systems References: <4C7B9327 DOT 9030204 AT graphtech DOT co DOT il> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 9/1/2010 1:12 PM, Magnus Holmgren wrote: > > To test this, I removed the call to sigproc_init in dll_crt0_0 and made sure > it was always called in dll_crt0_1 instead. Suddenly the sigp thread started > executing immediately, and its initialization was complete long before > wait_for_sigthread was called. Note that Christopher Faylor (cgf) just committed a change today (rev 1.383 dcrt0.cc) that removed the call to wait_for_sigthread() in dll_crt0_1(). -Edward PS. Thanks for looking into this! -- 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