This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: New STL implementation from SGI
- To: egcs at cygnus dot com
- Subject: Re: New STL implementation from SGI
- From: Nathan Myers <ncm at cygnus dot com>
- Date: Sun, 05 Jul 1998 17:26:23 -0700
- Newsgroups: cygnus.egcs
- Organization: http://www.cantrip.org/
- References: <x7sokk1h55.fsf.cygnus.egcs@peti.gmd.de>, <k2d8bm4x5k.fsf.cygnus.egcs@zero.aec.at>
Andi Kleen wrote:
>
> Nathan Myers <ncm@cygnus.com> writes:
>
> > Peter Simons wrote:
> >
> > > I just checked the latest STL release from SGI and was pleased to see
> > > that auto_ptr and a few other things have been fixed/added. I notice,
> > > though, that the latest egcs snapshot (obtained via CVS today) does
> > > still have the old STL implementation. Are there any plans to upgrade
> > > to the new STL before the next release?
> >
> > Probably we should do that.
>
> I have another related question. Does the all-singing, all-dancing, promised
> rewriten GNU C++ Library only cover the non STL parts [and still relies on
> the SGI codebase], or does it include a rewriten STL too?
The ASAD rewrite includes a (slightly modified) copy of SGI STL, currently
at release 3.1. Our goal is to have it identical, but that will depend
on (even more!) cooperation from Matt Austern at SGI.
Things left to do include putting "feature-select" macro guards around
the non-standard extensions and renaming some types and templates that
have "__" in their names. (These can interfere with name-mangling on
some targets.) Most of the other differences are in how things are
split up into files and how the files are found -- these make a difference
particularly when you want to keep track of (or avoid) the use of
extensions, or when you are ready to support separate template compilation.
There will be very good reasons to want to support separate template
compilation.
Nathan Myers
ncm@cantrip.org