From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>,
Benjamin Kosnik <bkoz@redhat.com>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: RFA (libstdc++): C++/v3 PATCH for c++/24163 (lookup in dependent bases) and c++/29131
Date: Sat, 28 May 2011 01:08:00 -0000 [thread overview]
Message-ID: <BANLkTimgO4m5XsBqhLz0HYrfyJ1VwYi3nQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=4+SxZ1+wJbjZkGXEjy28YZsKLYQ@mail.gmail.com>
On 27 May 2011 09:30, Jonathan Wakely wrote:
>
> I think this piece is also needed due to the fix for 29131:
>
> Index: include/std/thread
> ===================================================================
> --- include/std/thread (revision 174307)
> +++ include/std/thread (working copy)
> @@ -260,12 +260,6 @@
> #endif
>
> #ifdef _GLIBCXX_USE_NANOSLEEP
> - /// sleep_until
> - template<typename _Clock, typename _Duration>
> - inline void
> - sleep_until(const chrono::time_point<_Clock, _Duration>& __atime)
> - { sleep_for(__atime - _Clock::now()); }
> -
> /// sleep_for
> template<typename _Rep, typename _Period>
> inline void
> @@ -285,6 +279,12 @@
>
> ::nanosleep(&__ts, 0);
> }
> +
> + /// sleep_until
> + template<typename _Clock, typename _Duration>
> + inline void
> + sleep_until(const chrono::time_point<_Clock, _Duration>& __atime)
> + { sleep_for(__atime - _Clock::now()); }
> #endif
>
> _GLIBCXX_END_NAMESPACE_VERSION
>
> That only shows up if you configure with --enable-libstcxx-time
>
> I'll finish reg-testing it and submit it when I get home this evening.
>
2011-05-27 Jonathan Wakely <jwakely.gcc@gmail.com>
* include/std/thread (this_thread::sleep_until): Move after sleep_for.
Committed to trunk
prev parent reply other threads:[~2011-05-27 21:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 17:09 Jason Merrill
2011-05-20 18:26 ` Paolo Carlini
2011-05-20 19:46 ` Gabriel Dos Reis
2011-05-20 20:39 ` Jason Merrill
2011-05-20 21:56 ` Gabriel Dos Reis
2011-05-21 0:32 ` Joe Buck
2011-05-21 3:01 ` Christopher Jefferson
2011-05-21 3:44 ` Jason Merrill
2011-05-24 9:41 ` Jason Merrill
2011-05-24 11:50 ` Paolo Carlini
2011-05-24 18:51 ` Jason Merrill
2011-05-27 10:30 ` Jonathan Wakely
2011-05-27 12:26 ` Paolo Carlini
2011-05-27 12:34 ` Paolo Carlini
2011-05-28 1:08 ` Jonathan Wakely [this message]
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=BANLkTimgO4m5XsBqhLz0HYrfyJ1VwYi3nQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=bkoz@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=libstdc++@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).