On 18/11/20 20:22 +, Jonathan Wakely wrote:
On 18/11/20 00:01 +, Jonathan Wakely wrote:
On 14/11/20 14:23 +, Jonathan Wakely wrote:
On Sat, 14 Nov 2020, 13:30 Mike Crowe wrote:
@@ -195,7 +205,7 @@ namespace
if (__s.count() < 0) [[unlikely]]
return false;
-
On Wednesday 18 November 2020 at 20:22:53 +, Jonathan Wakely wrote:
> On 18/11/20 00:01 +, Jonathan Wakely wrote:
> > On 14/11/20 14:23 +, Jonathan Wakely wrote:
> > > On Sat, 14 Nov 2020, 13:30 Mike Crowe wrote:
> > > > > @@ -195,7 +205,7 @@ namespace
> > > > > if (__s.count(
On 18/11/20 00:01 +, Jonathan Wakely wrote:
On 14/11/20 14:23 +, Jonathan Wakely wrote:
On Sat, 14 Nov 2020, 13:30 Mike Crowe wrote:
@@ -195,7 +205,7 @@ namespace
if (__s.count() < 0) [[unlikely]]
return false;
- struct timespec rt;
+ syscall_times
On 14/11/20 14:23 +, Jonathan Wakely via Libstdc++ wrote:
On Sat, 14 Nov 2020, 13:30 Mike Crowe via Libstdc++,
wrote:
On Saturday 14 November 2020 at 00:17:59 +, Jonathan Wakely via
Libstdc++ wrote:
> On 32-bit targets where userspace has switched to 64-bit time_t, we
> cannot pass str
On Sat, 14 Nov 2020, 13:30 Mike Crowe via Libstdc++,
wrote:
> On Saturday 14 November 2020 at 00:17:59 +, Jonathan Wakely via
> Libstdc++ wrote:
> > On 32-bit targets where userspace has switched to 64-bit time_t, we
> > cannot pass struct timespec to SYS_futex or SYS_clock_gettime, because
>
On Saturday 14 November 2020 at 00:17:59 +, Jonathan Wakely via Libstdc++
wrote:
> On 32-bit targets where userspace has switched to 64-bit time_t, we
> cannot pass struct timespec to SYS_futex or SYS_clock_gettime, because
> the userspace definition of struct timespec will not match what the
On 32-bit targets where userspace has switched to 64-bit time_t, we
cannot pass struct timespec to SYS_futex or SYS_clock_gettime, because
the userspace definition of struct timespec will not match what the
kernel expects.
We use the existence of the SYS_futex_time64 or SYS_clock_gettime_time64
ma
