From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-481922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 101229 invoked by alias); 26 Mar 2015 21:41:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 101190 invoked by uid 48); 26 Mar 2015 21:41:31 -0000
From: "jaak at ristioja dot ee" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/60421] std::this_thread::sleep_for doesn't sleep for all arguments
Date: Thu, 26 Mar 2015 22:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 4.8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jaak at ristioja dot ee
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60421-4-gl5NtD21iw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60421-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60421-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-03/txt/msg03066.txt.bz2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60421

--- Comment #5 from Jaak Ristioja <jaak at ristioja dot ee> ---
(In reply to Jonathan Wakely from comment #4)
> Fixed for gcc5.

Looking at the diff <thread> of revision 221708, I fail to see how the

  if (__rtime <= __rtime.zero())
    return;

check in sleep_for() prevents the EINVAL in nanosleep(3p), as is the original
issue.

I mean aren't we dealing here with unsigned (decltype(_rtime)) to signed
(std::time_t) conversion?