X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<COL101-W27B90ED300AD81D50B68A0E65C0@phx.gbl>
From:	Jay <jay DOT krell AT cornell DOT edu>
To:	<cygwin AT cygwin DOT com>
Subject:	why the strange stack stuf in cygwin?
Date:	Mon, 1 Sep 2008 08:33:16 +0000
MIME-Version:	1.0
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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id m818Y7C5027883

 Why does Cygwin do such wierd stuff with the top of the stack?
 Is this to have thread locals faster than TlsGetValue offers?
 Is it worth it?
 (The cost: harder to LoadLibrary(cygwin1.dll), harder to port to other architectures,
  the strange path where DllMain "respawns", etc.)
 

 - Jay

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

- Raw text -