This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Complex log builtins
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Paul Brook <paul at codesourcery dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, ghazi at caip dot rutgers dot edu
- Date: 29 Aug 2004 16:28:51 +0200
- Subject: Re: Complex log builtins
- Organization: Integrable Solutions
- References: <200408291214.08573.paul@codesourcery.com>
Paul Brook <paul@codesourcery.com> writes:
| I just tried to make gfortran use the _Complex log builtins (clog, etc.), and
| discovered they don't exist.
|
| The original post adding the other C99 math functions
| (http://gcc.gnu.org/ml/gcc-patches/2003-09/msg00180.html)
| Mentions conflicts with C++ iostreams clog.
|
| However since these are C99 builtins they don't get enabled for C++ (right?).
Only under some circumstances, they are not enabled for C++. As a matter
of fact, some people wants them unconditionally, others don't. The
comprise was to have a switch that turns them on/off. But you can't assume
they're never enabled.
| I enabled the builtins and tried various combinations of clog,
| std::clog, ::clog and using namespace std; and couldn't trigger any bad
| behaviour. The C99 clog was uniformly ignored.
Could you post your testing programs?
| Can these builtins (clog, clogf and clogl) be enabled?
As discussed with Joseph S. Myers in another thread, what we should do
is to put GCC built-ins in a GCC name space, say "__gcc_". The reason
is that those are used by the middle-end which is language indendent
and should not dump C name space rules onto other languages. But, as
I understand it, we should coordinate these with Glibc people -- and I
remember Benjamin offering to look into this if I send him examples.
-- Gaby