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:message-id:date:from:mime-version:to:cc
	:subject:content-type:content-transfer-encoding; q=dns; s=
	default; b=w9lgArpFC11UYGh2w39FFMe8XZbIW4nw82nR2mgOR7XSOtIKilGY+
	upB35N+uK1ccgViqPnQJ32RLN3mTSAMRLtG9RSkuqSO+ZIcpijoSwZfzPLkCwXvy
	p7Rg24anDmB5s7l9WtxP5yNgs19x65NtAt9Aw+NxN9LdHqdBPTWy6Q=
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:message-id:date:from:mime-version:to:cc
	:subject:content-type:content-transfer-encoding; s=default; bh=v
	tQvQSm47xQ+WePJ0wrMdOX7gmw=; b=WRMJxgvRZtKgxIcEIJCzwHToKgjnOAAve
	ixxWRuX+Y8/BMDjHF4tDKkIpAz52qs7a/F4Y1nAZNpmHXaa/c96z7STKbC4Pu2oP
	Sli2lYheh5/ZMZlsPuKhmx1OdMyzjGTKA6ce6QqDYEmt6tP635oe81YJMEYhYMZB
	3hsYThsdCs=
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
X-Spam-SWARE-Status:	No, score=-4.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD autolearn=ham version=3.3.1
Message-ID:	<51670A56.6090701@alice.it>
Date:	Thu, 11 Apr 2013 21:09:10 +0200
From:	Angelo Graziosi <angelo DOT graziosi AT alice DOT it>
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version:	1.0
To:	Cygwin <cygwin AT cygwin DOT com>
CC:	fortran <fortran AT gcc DOT gnu DOT org>, Tobias Burnus <burnus AT net-b DOT de>
Subject:	Re: Cygwin with clock_gettime and CLOCK_MONOTONIC - gives always 0

Hi mum [1],

Corinna Vinschen wrote:

> Works fine for me with the current Cygwin 1.7.17, and the upcoming
> Cygwin 1.7.18:
>
>   $ cat > ct.c <<EOF

At each run, your test case almost always starts with the same value:

$ gcc -o ct ct.c

$ ./ct
tv_sec = 0, tv_nsec = 2793
tv_sec = 0, tv_nsec = 999989104
tv_sec = 2, tv_nsec = 15365
tv_sec = 3, tv_nsec = 17879

$ ./ct
tv_sec = 0, tv_nsec = 2793
tv_sec = 0, tv_nsec = 999990222
tv_sec = 1, tv_nsec = 999997765
tv_sec = 3, tv_nsec = 3911

$ ./ct
tv_sec = 0, tv_nsec = 2793
tv_sec = 0, tv_nsec = 999987428
tv_sec = 2, tv_nsec = 5587
tv_sec = 3, tv_nsec = 11453

$ ./ct
tv_sec = 0, tv_nsec = 2793
tv_sec = 0, tv_nsec = 999989942
tv_sec = 1, tv_nsec = 999996088
tv_sec = 3, tv_nsec = 2514

$ ./ct
tv_sec = 0, tv_nsec = 2793
tv_sec = 0, tv_nsec = 999990222
tv_sec = 2, tv_nsec = 4190
tv_sec = 3, tv_nsec = 11733

$ ./ct
tv_sec = 0, tv_nsec = 3073
tv_sec = 0, tv_nsec = 999989942
tv_sec = 1, tv_nsec = 999996926
tv_sec = 3, tv_nsec = 3911

[...]

I wonder if this is to be expected...

and, Tobias, why your test case [2] prints always "0" [3]? it looks very 
similar to that of Corinna.. oops mum.. ;-)


Ciao,
  Angelo.


---
[1] http://cygwin.com/ml/cygwin-apps/2013-04/msg00120.html
[2] http://gcc.gnu.org/ml/fortran/2013-04/msg00082.html
[3] http://gcc.gnu.org/ml/fortran/2013-04/msg00084.html

--
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

- Raw text -