This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: ostream and long long
- To: Gabriel Dos Reis <gdr at codesourcery dot com>
- Subject: Re: ostream and long long
- From: Andris Pavenis <andris at hal dot astr dot lu dot lv>
- Date: Thu, 26 Jul 2001 10:53:46 +0300 (EEST)
- cc: David Durham <david dot durham at wcom dot com>, <gcc-bugs at gcc dot gnu dot org>
On 25 Jul 2001, Gabriel Dos Reis wrote:
> Andris Pavenis <andris@hal.astr.lu.lv> writes:
>
> | On 24 Jul 2001, Gabriel Dos Reis wrote:
> |
> | > David Durham <david.durham@wcom.com> writes:
> | >
> | > | Well, with gcc 3.0 (solaris 2.5.1) compiling with c++ (as opposed to g++
> | > | or gcc)
> | >
> | > It seems like you didn't configure GCC with --enable-long-long. Did you?
> | >
> |
> | --enable-long-long is ignored unless large number of C99 functions
> | (like wide character functions, c99 mathematical functions and some
> | long long type related ones) are available. If You don't have at least
> | one it's ignored.
> |
> | Perhaps it would be better to test for functions really related to
> | using long long instead of binding it to support of many unrelated ones
>
> If --enable-long-long, then the accompanying C99 mathematical
> functions should be availble for long long support. They are not
> unreleated.
>
Do we really need sqrtf(), sqrtl(), sinl() and similar functions to
support long long? I think the best would be to check for functions
we really need for --enable-long-long instead of disabling it
if at least one of functions added with c99 is missing
Andris