On 04/09/19 18:21 +0100, Mike Crowe wrote:
On Wednesday 04 September 2019 at 17:57:45 +0100, Mike Crowe wrote:
On Wednesday 04 September 2019 at 17:14:30 +0100, Jonathan Wakely wrote:
> On 04/09/19 15:49 +0100, Mike Crowe wrote:
> > On Wednesday 04 September 2019 at 14:39:35 +0100, Jonathan Wake
On 04/09/19 15:49 +0100, Mike Crowe wrote:
On Wednesday 04 September 2019 at 14:39:35 +0100, Jonathan Wakely wrote:
On 15/07/19 17:47 +0100, Mike Crowe wrote:
> The pthread_cond_clockwait function was recently added[1] to glibc, and is
> due to be released in glibc 2.30. If this function is avai
On Wednesday 04 September 2019 at 14:39:35 +0100, Jonathan Wakely wrote:
> On 15/07/19 17:47 +0100, Mike Crowe wrote:
> > The pthread_cond_clockwait function was recently added[1] to glibc, and is
> > due to be released in glibc 2.30. If this function is available in the C
> > library it can be use
On 15/07/19 17:47 +0100, Mike Crowe wrote:
The pthread_cond_clockwait function was recently added[1] to glibc, and is
due to be released in glibc 2.30. If this function is available in the C
library it can be used it to fix
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41861 by supporting
std::chr
The pthread_cond_clockwait function was recently added[1] to glibc, and is
due to be released in glibc 2.30. If this function is available in the C
library it can be used it to fix
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41861 by supporting
std::chrono::steady_clock properly with std::conditio
