X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,SPF_HELO_PASS,TW_CG,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Magnus Holmgren Subject: Re: Cygwin slow on x64 systems Date: Tue, 31 Aug 2010 17:26:24 +0000 (UTC) Lines: 21 Message-ID: References: <4C7CA209 DOT 60603 AT onevision DOT de> <20100831140842 DOT GA11833 AT ednor DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) 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 Christopher Faylor cygwin.com> writes: > 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 think it makes sense, if the signal thread initialization takes time. Which it does: 69 15954 [main] date 2708 wait_for_sigthread: wait_sig_inited 0x4C 13706 29660 [main] date 2708 wait_for_sigthread: process/signal handling enabled, state 0x41 146 29806 [sig] date 2708 wait_sig: entering ReadFile loop, my_readsig 0xFC, my_sendsig 0x100 The above is a snippet from "strace date" (with some wrapping by me), using Cygwin 1.7.6 on Vista x64. And 1.7.7 is said to be slower still - and guess what, sigproc_init is called later; see r1.382 of dcrt0.cc. Magnus -- 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