public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: egcs@cygnus.com
Subject: new SGI STL: testing
Date: Sun, 12 Jul 1998 17:30:00 -0000	[thread overview]
Message-ID: <199807130030.RAA01986@atrus.synopsys.com> (raw)

I just run a test of the new SGI STL on sparc-sun-solaris2.5.1 with the
19980707 snapshot.  I replaced /libstdc++/stl with the new SGI STL,
except for the files

string
stdexcept
char_traits.h
stl_string_fwd.h

which I did not include.  All of the libstdc++ tests still pass, and
the g++ tests come out the same way.

I'm sure things went smoothly because the SGI group is using egcs in
their testing.

Some notes:

1) There are only 30 libstdc++ tests, and only 20 of the g++ tests use
any STL headers.  This is kind of weak coverage.

2) A patch will be needed for Linux/glibc2 systems; the patch whose
ChangeLog entry reads

----------------------------------------------------------------
Fri Feb 20 16:15:05 1998  H.J. Lu  (hjl@gnu.org)
                          Jason Merrill  <jason@yorick.cygnus.com>

        * ropeimpl.h: Check __STL_PTHREADS instead of _PTHREADS.
        * stl_alloc.h: Ditto.
        * stl_config.h: Ditto.
        * stl_rope.h: Ditto.

        * stl_config.h: include <_G_config.h> if __GNUG__ is defined.
        (__STL_PTHREADS): Defined if _PTHREADS is defined or
        __GLIBC__ >= 2.
----------------------------------------------------------------

should be redone for the new one.  It appears that the other fixes are
already in the new STL or are no longer needed.



                 reply	other threads:[~1998-07-12 17:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199807130030.RAA01986@atrus.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=egcs@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).