From: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
To: dvv@dvv.ru
Cc: mark@codesourcery.com, law@cygnus.com,
Gabriel.Dos_Reis@sophia.inria.fr, jason@cygnus.com,
kabatek@chemie.uni-halle.de, egcs@egcs.cygnus.com
Subject: Re: gcc-2.95 and SGI STL 3.2
Date: Wed, 30 Jun 1999 15:43:00 -0000 [thread overview]
Message-ID: <199906202022.WAA03885@mira.isdn.cs.tu-berlin.de> (raw)
Message-ID: <19990630154300.DoiVzWbn5FyvMFv34jZnMCEWL8uH4Lb96eHU0C48llA@z> (raw)
In-Reply-To: <37782349.124019584@localhost>
> >> STL 3.2 has one very important advantage (at least in things I'm
> >> involved in) - it is thread-safe.
[which class?]
> <string>, see the thread starting with
> http://egcs.cygnus.com/ml/egcs-bugs/1999-04/msg00771.html
In that case, updating STL won't give you anything: gcc does not use
<string> from STL. I don't know what the rationale is, but I
personally prefer the multithreading bug be fixed, instead of using a
completely different implementation.
As for libstdc++ v3: It seems there is yet another string
implementation, (apparently) contributed by Nathan Myers.
> Another STL-related (but not STL's) problem in the status quo (in 1.1.2,
> I haven't had enough time to check the latest snapshots, sorry) -
>
> T __default_alloc_template<0, 0>::.....
> ^
> in libstdc++ (that is non-thread-safe instantiations for lots of stuff),
> but it's kind of explicitly recognized in the bugs/todo list.
That is fixed in gcc 2.95, I believe.
Regards,
Martin
next prev parent reply other threads:[~1999-06-30 15:43 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-17 1:25 Ryszard Kabatek
1999-06-17 11:21 ` Martin v. Loewis
1999-06-18 3:28 ` Ryszard Kabatek
1999-06-18 11:23 ` Jason Merrill
1999-06-18 11:50 ` Gabriel Dos_Reis
1999-06-19 15:20 ` Jeffrey A Law
1999-06-19 16:07 ` Martin v. Loewis
1999-06-19 16:28 ` Joe Buck
1999-06-30 15:43 ` Joe Buck
1999-06-20 2:38 ` Jeffrey A Law
1999-06-20 7:51 ` Martin v. Loewis
1999-06-20 9:22 ` mark
1999-06-20 9:29 ` Dima Volodin
1999-06-20 10:17 ` Martin v. Loewis
1999-06-20 10:38 ` Dima Volodin
1999-06-20 13:27 ` Martin v. Loewis [this message]
1999-06-20 20:13 ` Benjamin Scherrey
1999-06-20 20:25 ` craig
1999-06-21 0:20 ` Steinar Bang
1999-06-21 2:16 ` Jeffrey A Law
1999-06-30 15:43 ` Jeffrey A Law
1999-06-30 15:43 ` Steinar Bang
1999-06-21 2:27 ` Jeffrey A Law
1999-06-30 15:43 ` Jeffrey A Law
1999-06-30 15:43 ` craig
1999-06-30 15:43 ` Benjamin Scherrey
1999-06-21 0:20 ` Steinar Bang
1999-06-21 1:11 ` Tim Waugh
1999-06-21 2:21 ` Steinar Bang
1999-06-30 15:43 ` Steinar Bang
1999-06-21 6:56 ` Dima Volodin
1999-06-22 0:01 ` Steinar Bang
1999-06-22 5:39 ` Dima Volodin
1999-06-22 13:45 ` Benjamin Kosnik
1999-06-30 15:43 ` Benjamin Kosnik
1999-06-23 10:25 ` Richard Henderson
1999-06-30 15:43 ` Richard Henderson
1999-06-30 15:43 ` Dima Volodin
1999-06-30 15:43 ` Steinar Bang
1999-06-30 15:43 ` Dima Volodin
1999-06-25 9:44 ` Joe Buck
1999-06-25 11:53 ` Tim Waugh
1999-06-30 15:43 ` Tim Waugh
1999-06-30 15:43 ` Joe Buck
1999-06-30 15:43 ` Tim Waugh
1999-06-30 15:43 ` Steinar Bang
1999-06-30 15:43 ` Martin v. Loewis
1999-06-30 15:43 ` Dima Volodin
1999-06-30 15:43 ` Martin v. Loewis
1999-06-30 15:43 ` Dima Volodin
1999-06-20 21:55 ` Jason Merrill
1999-06-21 2:06 ` Ryszard Kabatek
1999-06-30 15:43 ` Ryszard Kabatek
1999-06-30 15:43 ` Jason Merrill
1999-06-30 15:43 ` mark
1999-06-30 15:43 ` Martin v. Loewis
1999-06-30 15:43 ` Jeffrey A Law
1999-06-30 15:43 ` Martin v. Loewis
1999-06-20 8:58 ` Gabriel Dos_Reis
1999-06-30 15:43 ` Gabriel Dos_Reis
1999-06-30 15:43 ` Jeffrey A Law
1999-06-30 15:43 ` Gabriel Dos_Reis
1999-06-30 15:43 ` Jason Merrill
1999-06-30 15:43 ` Ryszard Kabatek
1999-06-30 15:43 ` Martin v. Loewis
1999-06-30 15:43 ` Ryszard Kabatek
1999-06-20 17:42 Phil Edwards
1999-06-30 15:43 ` Phil Edwards
1999-06-21 11:29 Mike Stump
1999-06-30 15:43 ` Mike Stump
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=199906202022.WAA03885@mira.isdn.cs.tu-berlin.de \
--to=martin@mira.isdn.cs.tu-berlin.de \
--cc=Gabriel.Dos_Reis@sophia.inria.fr \
--cc=dvv@dvv.ru \
--cc=egcs@egcs.cygnus.com \
--cc=jason@cygnus.com \
--cc=kabatek@chemie.uni-halle.de \
--cc=law@cygnus.com \
--cc=mark@codesourcery.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).