DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=l1O6uSVREW8XT798Mv2uWXyPklXI2FE1oqs1FkcPVy0j2KjsYhbuw
	SfMdv82LrUrKa5ZIcFaoXX8cPtLPQo9HvtUYQNI7lR9Gul0qHfcMZAkroAjYefcZ
	V7ydU56riAexyt3W7WJYi67hvlHFtmCrXN2scr+WhrZofYKDYq3CeQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 14 Mar 2014 17:42:43 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: With latest snapshot, emacs is very slow to start under X11
Message-ID: <20140314164243.GD2355@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <532325A5.5020103@cornell.edu> <53232E30.3080801@cornell.edu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="eRtJSFbw+EEWtPj3"
Content-Disposition: inline
In-Reply-To: <53232E30.3080801@cornell.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)

--eRtJSFbw+EEWtPj3
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mar 14 12:28, Ken Brown wrote:
> On 3/14/2014 11:52 AM, Ken Brown wrote:
> >With the snapshot of 2014-03-10, start the X server and then run
> >"emacs-X11 -Q&" in an xterm window.  On my system, emacs consistently
> >takes about 28 seconds to start.  With cygwin-1.7.28, however, it takes
> >about 1 second.  This is on Windows 7; so far I've tested 64-bit Cygwin
> >only.
> >
> >I'll try to find the first snapshot that exhibits the problem, and I'll
> >also test on 32-bit Cygwin.  But I wanted to make this preliminary
> >report quickly, in case the release of 1.7.29 is imminent.
>=20
> The problem first occurs with the snapshot of 2014-03-05, and it
> occurs only on 64-bit Cygwin.

The only possible explanation is the difference in installing the
exception handler, but this is quite puzzeling.  It's the same SEH
exception handler installation technique as any mingw64 application
uses and mingw64 applications are not known to be excessively slow.

In theory I'm on vacation, though, so I'll look into that next Monday at
the earliest.  If you want to test this yourself, try to build a Cygwin
DLL with just the patch from 2014-03-04 reverted so that a vectored
exception handler is used instead.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--eRtJSFbw+EEWtPj3
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTIzGDAAoJEPU2Bp2uRE+gOtsQAJXRGTAf4lUV+IZdgriqy6cC
aflT3EjpRCEM4dqOqUSoynzfO/cQj/40EA0y6n8olR1h79OYZJBRg3mbSAcb+OTN
l5K/rRWc+sPqKYnQA4Z1uU+NnDdeDFD2fSWiewgTKQJHqtPFQvNwQEgRVORhfJV6
kuBh7+LFwlNce8j6Xe/1pk0/1lUsEunquIZipLVW2ZL+3uT/J39KtonVSE1uLJTR
297Z5RMQHJunRzU173z6IPIC4Ex8S5Au6H49iS0L29jTRy0oiqznjLPBon9EgSnF
s7zP7xUBcs8G4y1RP8CCTwtt5GaMJhxJMAcfzTemWMV61MGC5okL1GpLAjT5Ge90
5dmmVKSik1UjTdBL+bZr8P9CXD24fY/ObDcEIS7vfDgD75yzazInuGkoOU8x80Ey
YYW+l3NfwxV7NtZ2/JNK0CDF4ZDJoY38sjy8xNkv+WJzHufmIugcp2lWeRCx5ZDm
jk2Sd9pJ9BAGr6JBYRlyzhD44D2TrwNPDE6DnFA2FO74ED+r2AYXxi0TIe+Ak8hT
/nvjgxJda2HPNG9rTKa/LEnfXiwinWMPEhG7CO9gCiJ6np5zhkiJjFUsSE4xpYFI
eWoIieAwV91iytg8kbSlbE0WNFbPPQvOew/6w7WdUZjHLexAHYA13RnSbdEVCkJg
4GAB4Pqh+lbbG+D1/X85
=jk8p
-----END PGP SIGNATURE-----

--eRtJSFbw+EEWtPj3--