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 Date: Mon, 11 Nov 2002 22:32:23 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Printf routine incorrectly prints NaN for -Inf Message-ID: <20021112033223.GA8423@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <000301c289f9$428771f0$a82ace84 AT research DOT pc DOT ece DOT mcgill DOT ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000301c289f9$428771f0$a82ace84@research.pc.ece.mcgill.ca> User-Agent: Mutt/1.5.1i On Mon, Nov 11, 2002 at 10:11:57PM -0500, Peter Kabal wrote: >gcc version 3.2 20020818 (prerelease) > >printf ("%g", log(0)); > >This prints "NaN" instead of "-Inf" as it should (and did in the past). >A check of the bit pattern returned shows that that log(0) returns a bit >pattern corresponding to "-Inf", but printf prints "NaN" instead. > >I am not sure which C library is being used (a bug report to gcc folks >got the response that newlib is the culprit). However, the compiler >option -print-libgcc-file-name tells me it is looking for libgcc.a. So I >am confused as to who to report the bug to. Perhaps unsurprisingly, the gcc folks are correct. It's a newlib bug. The newlib mailing list is newlib at sources dot redhat dot com . cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/