Takashi Yano wrote:
> > My workaround implementation of pthread_once (in gnulib) looks like this:
> >
> > /* This would be the code, for
> >typedef struct
> > {
> >pthread_mutex_t mutex;
> >_Atomic unsigned int num_threads;
> >_Atomic unsigned
On Wed, 29 May 2024 12:26:31 +0200
Bruno Haible wrote:
> Takashi Yano wrote:
> > As you mentioned in private mail to me, this seems to be a regression of
> > pthread::once() introduced by
> > commit 2c5433e5da8216aaf7458e50c63683c68fb0d3e8.
> >
> > I'll submit a patch for that issue shortly.
>
>
Takashi Yano wrote:
> As you mentioned in private mail to me, this seems to be a regression of
> pthread::once() introduced by
> commit 2c5433e5da8216aaf7458e50c63683c68fb0d3e8.
>
> I'll submit a patch for that issue shortly.
My workaround implementation of pthread_once (in gnulib) looks like thi
On Thu, 23 May 2024 20:09:09 +0200
Bruno Haible wrote:
> In Cygwin 3.5.3, on different machines, I see 3 Gnulib tests failing by
> timeout that worked perfectly fine in Cygwin 3.4.6 and older:
> FAIL: test-call_once2.exe
> FAIL: test-lock.exe
> FAIL: test-pthread-once2.exe
>
> Find here atta
Hi,
In Cygwin 3.5.3, on different machines, I see 3 Gnulib tests failing by
timeout that worked perfectly fine in Cygwin 3.4.6 and older:
FAIL: test-call_once2.exe
FAIL: test-lock.exe
FAIL: test-pthread-once2.exe
Find here attached a simplified version of test-pthread-once2.c.
Compile and r
5 matches
Mail list logo