This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: std::cout and long long problem
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Subject: Re: std::cout and long long problem
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 12 Feb 2001 17:32:35 -0200
- Cc: Gabriel Dos Reis <gdr at codesourcery dot com>, Craig Rodrigues <rodrigc at mediaone dot net>, libstdc++ at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <Pine.SOL.3.91.1010212101331.10975B-100000@taarna.cygnus.com>
On Feb 12, 2001, Benjamin Kosnik <bkoz@redhat.com> wrote:
>> Err... But since GCC supports it as an extension by default,
>> shouldn't libstdc++ support it by default too?
> look on the mailing list for this (old) thread. It's not gcc issues per
> se but "C" library header issues when we enable by long long by default.
> (lldiv_t in particular gives problems.)
Err.. If it's lldiv_t that gives problems, wouldn't it be the case to
have lldiv_t enabled/disabled separately in the OS bits, instead of
just throwing away all long-long support?
WRT OS bits, wouldn't it be reasonable to arrange for any C++
translation unit to implicitly #include the libstdc++ config bits
upfront? Adding `-include c++config.h' to the C++ specs doesn't seem
too much trouble to me.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me