ostream and long long

David Durham david.durham@wcom.com
Thu Jul 26 13:31:00 GMT 2001

Um.. the first time I compiled 3.0,  gcc-2.95.3 was the boot strapp'en

All subsequent compiles have been from the previous 3.0 compile...

For now, I've just switched back to 2.95.2, where ostream<<long long is
supported in that stdc++ implementation

I switched back for 3 main reasons really:
   1) gcc-3.0 is a good bit slower compiling
   2) gcc-3.0 on sparc-solaris-2.5.1 has an 8 bit bool type, where it
was 32 bit previously.  We have some legacy libraries that expect a bool
* to point to 32 bits
   3) gcc-3.0 does have either some or all of long long support in its

I've heard a rumor that 3.1 will be released before too long.  And that
it is supposed to be a good bit faster compiling.   Eventually, it will
fully support long long in its libraries.  And now that bools are 8 bit,
I need to make careful changes to the header files of our legacy
libraries and recompile.

I was hoping it would be a simple compile and go situation to move to
gcc-3, but it has turned out not to be the case.  That's fine... we
didn't *really* need to upgrade anyway.  And hopefully 3.1 will resolve
some of these issues.  And when I get time I'll work out the rest.


On 26 Jul 2001 16:15:19 -0400, Phil Edwards wrote:
> David, what compiler are you using to bootstrap?  It /should/ be a silly
> question, since libstdc++ uses the freshly-built g++ to do its work, but
> another user is reporting a similar "should be enabled but isn't" problem;
> he gets it working when building 3.0 with RH's 2.96, but not if he builds
> 3.0 with 2.92.3 or older egcs.
> Phil

More information about the Gcc-bugs mailing list