X-Spam-Check-By: sourceware.org Message-ID: <4403958A.8050007@redhat.com> Date: Mon, 27 Feb 2006 19:12:58 -0500 From: Jeff Johnston User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) MIME-Version: 1.0 To: newlib AT sources DOT redhat DOT com Cc: cygwin AT cygwin DOT com Subject: Re: gcc-3.4.4-1: c++: cmath: calling std::isnan results in endless loop References: <01d101c63bb9$ef9ead20$a501a8c0 AT CAM DOT ARTIMI DOT COM> <44033332 DOT 7020801 AT redhat DOT com> <20060227172100 DOT GJ30238 AT calimero DOT vinschen DOT de> <44034757 DOT 8090109 AT redhat DOT com> In-Reply-To: <44034757.8090109@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Jeff Johnston wrote: > Corinna Vinschen wrote: > >> Jeff, >> >> On Feb 27 12:13, Jeff Johnston wrote: >> >>> Gabriel Dos Reis wrote: >>> >>>> yes, isnan and friends are supposed to be macros only, not functions. >>> >>> >>> I'll start working on a newlib patch for this. >> >> >> >> while you're at it, please do *not* remove the isnan function >> implementation. It's still required to run applications which >> have been linked against older newlib versions. Just adding >> a isnan macro should be sufficient, shouldn't it? >> >> > > Yep, way ahead of you :). I will rename the current implementations to > be double-underscored, have the macros call these, and have > non-underscored versions that directly call the underscored versions. I > think that should satisfy all concerns. > > -- Jeff J. > I have just checked in a solution. Builds fine for x86-linux and I verified both the new macro versions work and the old function names can be called. Let me know if anything breaks that I didn't anticipate. -- Jeff J. -- 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/