This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: conflict between libstdc++ nan and c99/builtin nan functions
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Cc: gcc-bugs at gcc dot gnu dot org, gcc at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Date: 28 Nov 2002 16:14:22 +0100
- Subject: Re: conflict between libstdc++ nan and c99/builtin nan functions
- Organization: Integrable Solutions
- References: <200211281447.JAA16991@caip.rutgers.edu>
"Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> writes:
| I'm getting this warning (several times) when building libstdc++-v3:
|
| > libstdc++-v3/libmath/mathconf.h:84: warning: conflicting types for
| > built-in function `nan'
|
| mathconf.h contains:
|
| > #ifndef NAN
| > # define NAN (nan())
| > double nan (void);
| > #endif
Now that we have built-in NaNs (thanks rth!), this hackery should just
go away.
[...]
| My question is whether libstdc++-v3 needs to provide `nan' as an
| exportable function or whether it just needs it internally.
It just used it internally (I can't recall for what exactly)
| If it's
| just internally, perhaps I can change the NAN macro to just call
| __builtin_nan(""), otherwise I'll correct the definition in nan.c.
Well, the NAN thingy should be removed.
Thanks,
-- Gaby