Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: Date: Wed, 6 Jul 2005 04:15:05 -0400 From: Lev Bishop Reply-To: Lev Bishop To: cygwin AT cygwin DOT com Subject: Re: SV: Bug in printf ? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <6879888 DOT 1120133556579 DOT JavaMail DOT adm-moff AT moffice2 DOT nsc DOT no> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j668FOti015001 On 06/07/05, Lev Bishop wrote: > 4) I have no idea what mingw is doing, but it's different to the > above. Gcc constructs the same double precision constants as on cygwin > but strtod() is different and seems to have less precision, and > printf() seems to work with about 16 digits precision. At a glance I'd > say it rounds to zero, with exactly the precision of ... the precision of a raw double. Ie, it looks like the cygwin build works slightly nicer than mingw with plenty of extra precision for conversions to and from decimal, and round-to-even for runtime conversions, which is a good thing. -- 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/