This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/50834] Documentation about STL thread safety is ambiguous
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 22 Oct 2011 22:26:56 +0000
- Subject: [Bug libstdc++/50834] Documentation about STL thread safety is ambiguous
- Auto-submitted: auto-generated
- References: <bug-50834-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50834
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |documentation
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2011-10-22
AssignedTo|unassigned at gcc dot |redi at gcc dot gnu.org
|gnu.org |
Ever Confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-10-22 22:26:56 UTC ---
The first piece you quote continues "unless otherwise documented as safe" and
the SGI definition documents what is safe for concurrent reads.
But I agree it could be improved, the C++11 standard has a better definition,
which we aim to conform to.