X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=FxzvNz
	O68WY6wK3TdcraqHfR/uT6vNS4wturWDXF+19PDY8MH7bA5Z/oSoaQovLPNZrCmp
	+QISMYLQQgxR4AAjw049tiY2+qyO9m4kFf6fc+Xqzq5zCR9dIJO0K02bvuyLYImW
	v24ERy9Ht0/pe4lJcJS7xtAgz+yjpoaIojvE0=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; s=default; bh=5USdryQQjyjZ
	6MXdsa7ZqK9WEiU=; b=PtmF4kfCxLg4UT68cZb8LkFaR2yvzlKdfVkRBON1bIXb
	xhl6ESzPpbyEfSr0fhhoWBcw6MFmnbNNBVpZqtwgsXWOjocumCebLINL+DJFOBa8
	hvZBirVjVIJWukOYJsbS/Gc9abmnxJec+g/hDU6vwNHbsLOXOPq49SeZXOzTYgk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=pln, 2nd, pts, H*F:D*nl
X-HELO: lb1-smtp-cloud8.xs4all.net
Date: Tue, 27 Nov 2018 11:19:46 +0100
Message-ID: <290b7d0bafa41fac883c788b75e41b1f@smtp-cloud8.xs4all.net>
From: Houder <houder AT xs4all DOT nl>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: No thread safety in clock_gettime (hires_ns::prime)
References: <CAOWZHxdJi1E9APtSXm35LkDU33VqGZSwnGtvOfdHA9PTTJgRjQ AT mail DOT gmail DOT com> <20181126170140 DOT GO30649 AT calimero DOT vinschen DOT de> <093958e15892f03eecfe6eea1ce6566f AT smtp-cloud7 DOT xs4all DOT net> <20181127093738 DOT GA3928 AT calimero DOT vinschen DOT de>
In-Reply-to: <20181127093738.GA3928@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=fixed
User-Agent: mua.awk 0.99

On Tue, 27 Nov 2018 10:37:38, Corinna Vinschen  wrote:
> 
> On Nov 26 19:07, Houder wrote:
[snip]

> > 64-@@ uname -a
> > CYGWIN_NT-6.1 Seven 2.11.3(0.329/5/3)  x86_64 Cygwin
> > 64-@@ ls -l /bin/cygwin1*
> > -rwxr-xr-x 1 Henri None 3339661 Nov  8 14:36 /bin/cygwin1-2.11.2.X
> > -rwxr-xr-x 1 Henri None 3337995 Nov 26 18:43 /bin/cygwin1-64-20181126.X
> > -rwxr-xr-x 1 Henri None 3337995 Nov 26 18:43 /bin/cygwin1.dll
> > 64-@@ cd threads
[snip]

> > 64-@@ for loop in {1..10000}; do ./cyg_hires_clock_race.exe; done
> > 64-@@# That is enough!
> 
> Thanks a lot for testing!  (Particulary since I couldn't even
> reproduce this on W7)

Perhaps my machine is a bit "peculiar" ... :-)
(the real litmus test is, of course, James E. King III's application, not the STC)

Henri

/home/corinna/src/cygwin/cygwin-2.11.2/cygwin-2.11.2-1.i686/src/newlib-cygwin/winsup/cygwin/cygheap.cc
64-@@ uname -a
CYGWIN_NT-6.1 Seven 2.11.2(0.329/5/3) 2018-08-31 13:05 x86_64 Cygwin

64-@@ cd threads
64-@@ for loop in {1..1000}; do ./cyg_hires_clock_race.exe; done
ERROR: one of the timespec structures was zero:
main thread: tv_sec =       3455 tv_nsec =  350898985
 2nd thread: tv_sec =          0 tv_nsec =          0
64-@@ for loop in {1..1000}; do ./cyg_hires_clock_race.exe; done
ERROR: one of the timespec structures was zero:
main thread: tv_sec =       3461 tv_nsec =  157276019
 2nd thread: tv_sec =          0 tv_nsec =          0
ERROR: one of the timespec structures was zero:
main thread: tv_sec =       3467 tv_nsec =  493831379
 2nd thread: tv_sec =          0 tv_nsec =          0
ERROR: one of the timespec structures was zero:
main thread: tv_sec =       3467 tv_nsec =  855769393
 2nd thread: tv_sec =          0 tv_nsec =          0

Perhaps the following is significant?

64-@@ cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 60
model name      : Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
stepping        : 3
cpu MHz         : 3398.000
cache size      : 8192 KB
...

processor       : 7
vendor_id       : GenuineIntel
cpu family      : 6
model           : 60
model name      : Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
stepping        : 3
cpu MHz         : 3398.000
cache size      : 8192 KB
physical id     : 0
siblings        : 8
core id         : 3
cpu cores       : 4
apicid          : 7
initial apicid  : 7
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca \
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pni dtes64 \
monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm sse4_1 sse4_2 \
x2apic movbe popcnt aes xsave osxsave avx f16c rdrand lahf_lm ida arat \
epb xsaveopt pln pts dtherm fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid
clflush size    : 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

=====


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple