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
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: loading of wsock32 disturbs FPU
Date: Wed, 2 Mar 2005 18:42:13 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20050302174057.GC21935@trixie.casa.cgf.cx>
Message-ID: <SERRANOkK5LqN33HFnw00000052@SERRANO.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 02 Mar 2005 18:42:13.0716 (UTC) FILETIME=[8CF13140:01C51F57]

----Original Message----
>From: Christopher Faylor
>Sent: 02 March 2005 17:41

> 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


 I refer you to my previous post!   :)


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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