Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 2 Mar 2005 13:48:27 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: loading of wsock32 disturbs FPU Message-ID: <20050302184827.GA23066@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20050302174057.GC21935@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Wed, Mar 02, 2005 at 06:42:13PM -0000, Dave Korn wrote: >----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... > > I refer you to my previous post! :) Ditto. 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/