Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date:	Wed, 2 Mar 2005 12:40:57 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: loading of wsock32 disturbs FPU
Message-ID:	<20050302174057.GC21935@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
References:	<20050302143149 DOT GA3187 AT cygbert DOT vinschen DOT de> <SERRANOMwVN7miR9Odu0000004d AT SERRANO DOT CAM DOT ARTIMI DOT COM>
Mime-Version:	1.0
In-Reply-To:	<SERRANOMwVN7miR9Odu0000004d@SERRANO.CAM.ARTIMI.COM>
User-Agent:	Mutt/1.4.1i

On Wed, Mar 02, 2005 at 05:21:55PM -0000, Dave Korn wrote:
>And I can confirm that adding 'asm ("finit");' to wsock_init (I put it
>inside the "if (!wsock_started)" clause, just after the closing brace
>of the "if (wsastartup)" clause) fixes both the testcase that Ralf
>posted this morning and also fixes his original example code so that it
>produces the same results whether or not the hostname call is made.
>(It doesn't of course fix the problem if the user calls LoadLibrary
>directly on either ws2_32 or msvcrt, but we don't expect it to, we just
>want the cygwin library calls to not have unexpected side-effects!)

But unconditionally calling "finit" will guarantee unexplained side-effects...

cgf

--
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 -