X-Spam-Check-By: sourceware.org To: "Dave Korn" Cc: , , Subject: Re: gcc-3.4.4-1: c++: cmath: calling std::isnan results in endless loop References: <01d101c63bb9$ef9ead20$a501a8c0@CAM.ARTIMI.COM> From: Gabriel Dos Reis In-Reply-To: <01d101c63bb9$ef9ead20$a501a8c0@CAM.ARTIMI.COM> Date: 27 Feb 2006 17:59:56 +0100 Message-ID: Lines: 20 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 "Dave Korn" writes: [...] | It looks to me like the cygwin/newlib combination is not being compliant if | it implements isnan as a function rather than a macro. I couldn't see | anything in the standard that says it can be a function, and every reference | to it describes it as a macro, not a function. It may be the case that | libstdc++ is within its rights to assume that isnan is a macro after all. yes, isnan and friends are supposed to be macros only, not functions. | OTOH it may be that libstdc++ was only supposed to be shadowing those ctype | macros that are guaranteed to have underlying function implementations; I | don't know what the shadowing is for, so I can't comment. libstdc++ is supposed to shadow ctype macros -- and it also expect them to have a function implementation. -- Gaby -- 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/