public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/56002] [C++11] allow generic locks to be used without requiring plattform support for threads
Date: Sat, 16 Mar 2013 20:23:00 -0000	[thread overview]
Message-ID: <bug-56002-4-CZ6qw1HkDB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56002-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56002

--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> 2013-03-16 20:22:40 UTC ---
Author: redi
Date: Sat Mar 16 20:22:30 2013
New Revision: 196710

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=196710
Log:
    PR libstdc++/56002
    * include/std/mutex (lock_guard, unique_lock, lock): Define without
    depending on _GLIBCXX_HAS_GTHREADS.
    * testsuite/30_threads/lock_guard/cons/1.cc: Run on all targets.

Modified:
    branches/gcc-4_7-branch/libstdc++-v3/ChangeLog
    branches/gcc-4_7-branch/libstdc++-v3/include/std/mutex
   
branches/gcc-4_7-branch/libstdc++-v3/testsuite/30_threads/lock_guard/cons/1.cc


  parent reply	other threads:[~2013-03-16 20:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 12:21 [Bug libstdc++/56002] New: [mutex] allow generic classes " npl at chello dot at
2013-01-16 12:25 ` [Bug libstdc++/56002] " redi at gcc dot gnu.org
2013-01-17 15:07 ` [Bug libstdc++/56002] [C++11] allow generic locks " daniel.kruegler at googlemail dot com
2013-01-17 16:19 ` redi at gcc dot gnu.org
2013-01-17 20:44 ` npl at chello dot at
2013-03-16 19:46 ` redi at gcc dot gnu.org
2013-03-16 19:53 ` redi at gcc dot gnu.org
2013-03-16 20:23 ` redi at gcc dot gnu.org [this message]
2013-03-24 17:52 ` redi at gcc dot gnu.org

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=bug-56002-4-CZ6qw1HkDB@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).