From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [patch] libstdc++/58038 libstdc++/60421 fix overflows in std::this_thread::sleep_for()
Date: Sat, 11 Apr 2015 11:50:00 -0000 [thread overview]
Message-ID: <20150411115051.GE9755@redhat.com> (raw)
In-Reply-To: <20150326195919.GM9755@redhat.com>
On 26/03/15 19:59 +0000, Jonathan Wakely wrote:
>We have a couple of bugs where durations with unsigned representations
>result in negative or huge time_t values, which result in not sleeping
>at all or sleeping for billions of years (or merely for decades if you
>have a 32-bit time_t).
>
>This change simply returns early for time points in the past or
>negative durations.
>
>Tested x86_64-linux, powerpc64le-linux, committed to trunk.
Also committed to the 4.9 branch.
prev parent reply other threads:[~2015-04-11 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 19:59 Jonathan Wakely
2015-04-11 11:50 ` 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=20150411115051.GE9755@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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).