X-Recipient: archive-cygwin AT delorie DOT com
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=obXVGsDN3ixt+vH4TnSJlwbNd/FUI676kMOJJOYpMDG2nm+ODWoav
	sCJnrpKr+SK34Jud6n5VqrAeFQAp0xw7traGqUAi0MUKgmL/dzCUnEUm+/+YoW1d
	ShnICZIEdtE+mm8FFphr255odkF6wYhONV9kSElpBidCrAoYQrsMow=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default;
	 bh=0p0B+5q+/FMg2Vk/GH+bamsU1a8=; b=tbZO7eLcuGTgnd0ligT3ZmYCdjxm
	izQR9y6BYevBsm5ZTGqq+2NMLXI0LfLOgUctOI2RrUXMPzMMg4ujiZf2xqVObhGJ
	ICAs18vDhubDI0fwj7n3oTzzlf9GiDH+NThZLFP3HhJfGcrEMrme4QING73D0ryo
	0plUu0Pnanalz1g=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-6.0 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO: calimero.vinschen.de
Date: Sat, 25 Jan 2014 12:59:58 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Maintainer for git?
Message-ID: <20140125115958.GU2357@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CA+kUOanN3FjBzQ1HRPtmXfxLSbHps5WkkqrHqw8qK6FhX8aTgw AT mail DOT gmail DOT com> <CAAXzdLV_xoMM59H_6fnTgRSAVhs4FLRaMyEL9e1WBzUp4SWR8g AT mail DOT gmail DOT com> <CA+kUOakGhMYEP5kjmLk1HeWTi9QNTp1Fnk5YF3JuqR_fUc6hPg AT mail DOT gmail DOT com> <20140115105534 DOT GB31912 AT tastycake DOT net> <CAAXzdLX0YQTBVOkjUq3f-Jr03Cx5PzsY3_gRYO9rpp_GXOQKYw AT mail DOT gmail DOT com> <CALgEz7qhf85-kdBCqFWWjni8rw8iTvabtdnBu=z4-tVmy_+jTg AT mail DOT gmail DOT com> <CAAXzdLXQ-MfUQj6Zh4FSCgGgwwZ82OpkPTWznp5vVFXXeeKvHw AT mail DOT gmail DOT com> <CALgEz7o7Sm2+NF=Fc3Wpp+Fy=+LQiz0aAc-+Pp+s=-Pjw--AuQ AT mail DOT gmail DOT com> <CAM7Q9ZvnA4ukDXdbQExX7mje=6yx=0STzQTKAbWhG3jApGHmJw AT mail DOT gmail DOT com> <20140123105142 DOT GN2357 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="Idd68gPqKLz5+Ci0"
Content-Disposition: inline
In-Reply-To: <20140123105142.GN2357@calimero.vinschen.de>
User-Agent: Mutt/1.5.21 (2010-09-15)

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

On Jan 23 11:51, Corinna Vinschen wrote:
> On Jan 22 16:42, Chris O'Bryan wrote:
> > > On Mon, Jan 20, 2014 at 5:31 PM, Steven Penny wrote:
> > >
> > >> Are you certain the bug is present in Adam=E2=80=99s version? He has=
 tested it here
> > >>
> > >>     http://cygwin.com/ml/cygwin/2014-01/msg00085.html
> > >
> > > I just tried cloning something big again (the linux kernel). See
> > > below. The first one was with git-1.7.9 the default Cygwin version.
> > >[...]
> > > x86$ git clone https://git.kernel.org/pub/scm/linux/kernel/git/torval=
ds/linux.git
> > > linux-git-1.8.5.2
> > > Cloning into 'linux-git-1.8.5.2'...
> > > remote: Counting objects: 3366700, done.
> > > remote: Compressing objects: 100% (508113/508113), done.
> > > remote: Total 3366700 (delta 2833563), reused 3362434 (delta 2829537)
> > > Receiving objects: 100% (3366700/3366700), 703.64 MiB | 2.16 MiB/s, d=
one.
> > > fatal: pack is corrupted (SHA1 mismatch)
> > > fatal: index-pack failed
> > >[...]
>=20
> Even if it's an OpenSSL issue, I'm not sure what to do about it.  I'm
> building OpenSSL for Cygwin, but I have no knowledge of the crypto
> stuff...
>=20
> I don't see anything unusual in the build process, except, maybe, that
> for SHA1 the x86 assembler code is used.  I'm wondering what happens
> when taking out -DSHA1_ASM from the build process.  Or what happens when
> using -O2 instead of -O3.

I have a hunch that this is not a OpenSSL but a Cygwin problem.

The default case in OpenSSL is to use SSE2 instructions in the x86
assembler code.  However, SSE2 instructions utilize the x86 XMM
registers, which are not saved and restored in setjmp/longjmp, nor are
they stored and restored in signal handling under Cygwin.

In the long run Cygwin should save and restore the XMM registers on
x86 as well, I guess.

For the time being, I've build a new OpenSSL version 1.0.1f-2 with the
"no-sse2" flag.  With this version I could clone the linx repo without
error.  Please give it a try.


Corinna

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

--Idd68gPqKLz5+Ci0
Content-Type: application/pgp-signature

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

iQIcBAEBAgAGBQJS46c+AAoJEPU2Bp2uRE+g5RwP/24OduUZezFGGFydt6Uupwn2
/q7tT39OTw0dJ41UWys2gzYrzTijf+a6sIKKdfSpPp/RyMqmxvQYLA97WmxBmcji
kDgN7kefvlfXscvf9dUzmzG953QEbOkZEL50pMs6dqonzi95wntfKHmjFAoSQ/bB
SsZRDFQncAKy0XT3hl+enXejy4zo/EsExWX9zbMoKglhUII4Ap4iOzdWRRr+TEFv
i9XRd68OXRdMNex1CG2boNomGbtgBqe3ArjChO5Dbp5hBEk2znYgzlJZjk0GQJNZ
wsrODNtDQp6Jcy3K7lRTHNlQ/8uAAiOyJtu6Uu4X+A1N5YnMJ3WRreHwA42Rp2Jj
zO7RVPjURMD95w4bBmKcK4qcQPuO7RTR8rSKVdOnnh3wBFBblMJFrQwGX+uSOcfb
wdJYrehncfvr5MvQm9Pb0GY2sg9h6LslGUlowcAcPCVjbJ+A8GnZNHx1rLodf0G8
SBGZZke6z8TMA6BYX0k1uPZYwpcmzZNLp15aOlKJ7gd/cjWGRuOFSu3frLO6hYmg
bkT0ouVRA2/A2IqfchwQQsiOI5mqiPeNA5WTt0KQYJcsfK/aWXpvUnlC91oqpLqj
hIxIAutgfkC5nlp6v/UydZb4X8qKd1P1KbSBGrhG7seroLwUSDNzMKXsh22Q12r3
gORChOk6oIb3oGtp/brF
=NZW8
-----END PGP SIGNATURE-----

--Idd68gPqKLz5+Ci0--