public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pollard <andrewp@andypo.net>
To: ljrittle@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/5432: Implementation still not thread-safe on multiprocessor machines
Date: Mon, 18 Feb 2002 15:46:00 -0000 [thread overview]
Message-ID: <20020218234607.10548.qmail@sources.redhat.com> (raw)
The following reply was made to PR libstdc++/5432; it has been noted by GNATS.
From: Andrew Pollard <andrewp@andypo.net>
To: rodrigc@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc: andrew@andypo.net, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
ljrittle@gcc.gnu.org
Subject: Re: libstdc++/5432: Implementation still not thread-safe on multiprocessor machines
Date: Mon, 18 Feb 2002 23:34:46 GMT
>Synopsis: Implementation still not thread-safe on multiprocessor machines
>
>State-Changed-From-To: feedback->closed
>State-Changed-By: rodrigc
>State-Changed-When: Sun Feb 17 18:54:57 2002
>State-Changed-Why:
> Fixed in recent gcc 3.1 snapshots.
>
>http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5432
Cheers. I have verified that the 3.1 source "works as expected".
Shame it couldn't make it into gcc-3.0.4, I'll just have to patch locally
once gcc-3.0.4 is out...
Andrew.
--
Andrew Pollard, ASI/Brooks Automation | home: andrew@andypo.net
670 Eskdale Road, Winnersh Triangle, UK | work: Andrew.Pollard@brooks.com
Tel/Fax:+44 (0)118 9215603 / 9215660 | http://www.andypo.net
next reply other threads:[~2002-02-18 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 15:46 Andrew Pollard [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-17 18:54 rodrigc
2002-01-24 13:26 ljrittle
2002-01-23 23:49 ljrittle
2002-01-19 7:26 andrew
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=20020218234607.10548.qmail@sources.redhat.com \
--to=andrewp@andypo.net \
--cc=gcc-prs@gcc.gnu.org \
--cc=ljrittle@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).