public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Loren James Rittle <rittle@latour.rsch.comm.mot.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/5037: Multithreaded read access to strings not threadsafe on Solaris/Sparc
Date: Thu, 06 Dec 2001 15:36:00 -0000 [thread overview]
Message-ID: <20011206233601.1504.qmail@sources.redhat.com> (raw)
The following reply was made to PR libstdc++/5037; it has been noted by GNATS.
From: Loren James Rittle <rittle@latour.rsch.comm.mot.com>
To: ckaes@jabber.com, ljrittle@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org
Subject: Re: libstdc++/5037: Multithreaded read access to strings not threadsafe on Solaris/Sparc
Date: Thu, 6 Dec 2001 17:25:58 -0600 (CST)
OK, thanks for investigating the obvious possible problem. I think
someone that knows the sparc processor and multiprocessor architectures
based on it would have to double check the contents of that file.
I have access to a multiprocessor sparc-sun-solaris2.6 machine and
I have confirmed the problem in that environment with gcc 3.0
and the pending 3.0.3 prerelease...
(BTW, sorry, the extra information I requested was available in bugger.ii
that you included in your report.)
next reply other threads:[~2001-12-06 23:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 15:36 Loren James Rittle [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-02 22:17 ljrittle
2001-12-26 21:33 ljrittle
2001-12-06 16:36 Loren James Rittle
2001-12-06 13:56 Craig
2001-12-06 13:16 ljrittle
2001-12-06 13:08 ljrittle
2001-12-06 9:26 ckaes
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=20011206233601.1504.qmail@sources.redhat.com \
--to=rittle@latour.rsch.comm.mot.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/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).