current status of v3

[Phil Edwards]

On Wed, Oct 25, 2000 at 09:42:51AM +0200, Levente Farkas wrote:
> Phil Edwards wrote:
> > > it's the default stdc++ in the gcc cvs tree ?
> > 
> > Eventually.
> > 
> > > and what does it mean ? if I compile gcc than it'll use v3 ?
> > 
> > --enable-libstdcxx-v3
> > 
> > (it's one word!  there are no spaces!  :-)
> 
> this means v3 is NOT the default since without this configure settings
> gcc use v2! or am I wrong ?
> or what the "Eventually." mean ?

That's precisely the current situation.  By default, gcc 2.9x will use v2.
With --enable-libstdcxx-v3, gcc will use the v3 library.  Also, -fhonor-std
is turned on by default.  Configure options like --enable-namespaces are
no longer needed.

GCC 3.0 will use v3 by default.


> > > what about the new abi ? do I need use --enable-new-gxx-abi ?
> > 
> > Experimental.
> > 
> > > the current stdc++ compile and run without the new abi ?
> > 
> > Probably.
> 
> so I don't have to use the --enable-new-gxx-abi ?
> or it's better if I use it ?

The current compiler and library will probably run better without the
new ABI.  It's still experimental.  GCC 3.0 will use the new ABI, so you
can turn it on if you want to test it or debug it.

I haven't even looked at the new ABI, so I can't answer anything else.

Phil