X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,MIME_QP_LONG_LINE X-Spam-Check-By: sourceware.org Message-ID: <421404.53076.qm@web25504.mail.ukl.yahoo.com> Date: Wed, 2 Sep 2009 06:58:58 +0000 (GMT) From: Marco Atzeri Subject: Re: std::arg() bug : not repetitive ? To: cygwin AT cygwin DOT com, Dave Korn In-Reply-To: <4A9DC24F.4070309@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com --- Mer 2/9/09, Dave Korn ha scritto: =20 > =A0 Bah.=A0 Still, at least the -ffloat-store > workaround still helps, for this > case at any rate..=A0 Also, if you get GCC to use SSE > instructions, there's no > issue with excess precision: >=20 > > $ g++-4 comp_2.cc -o0 -o comp_2 -I > /usr/include/octave-3.2.0/octave -march=3Dpent > > ium4 -msse -mfpmath=3Dsse > >=20 > > $ ./comp_2.exe > > 0.785398 > > 0.785398 > > 0 > > 0 > >=20 > > $ Are this setting acceptable for a cygwin package ? -march=3Dpentium4 -msse -mfpmath=3Dsse >=20 > =A0 However it does look like it's not going to get > fully fixed for C++ until > someone with some serious language-lawyering skills can > spend some time > defining the exact semantics. Not me. ;-( >=20 > =A0 =A0 cheers, > =A0 =A0 =A0 DaveK >=20 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple