This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin with clock_gettime and CLOCK_MONOTONIC - gives always 0
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Cc: fortran at gcc dot gnu dot org
- Date: Thu, 11 Apr 2013 22:46:05 +0200
- Subject: Re: Cygwin with clock_gettime and CLOCK_MONOTONIC - gives always 0
- References: <5166A0B3 dot 70801 at net-b dot de> <5166BCA1 dot 5040204 at net-b dot de> <20130411134835 dot GD18333 at calimero dot vinschen dot de> <51670B6B dot 3000503 at net-b dot de> <20130411195200 dot GJ18333 at calimero dot vinschen dot de> <51671EAA dot 8030901 at net-b dot de>
- Reply-to: cygwin at cygwin dot com, fortran at gcc dot gnu dot org
On Apr 11 22:35, Tobias Burnus wrote:
> Corinna Vinschen wrote:
> >On Apr 11 21:13, Tobias Burnus wrote:
> >>Where is actually the source code of the clock_gettime, which Cygwin
> >>uses? I thought that it was newlib. But looking at
> >>the code should return -1 for "clock_gettime (CLOCK_MONOTONIC" as
> >>CLOCK_MONOTONIC (= 4) is not handled, only CLOCK_REALTIME (= 1,
> >>according to src/newlib/libc/include/time.h).
> >>However, as both you and Angelo get a zero return value, I must look
> >>at the wrong file.
> >Yes, for Cygwin it's
> Well, it's "times.cc" not "timer.cc". I think the problem with
> Cygwin was a red herring. But there are a bunch of problems:
> a) Angelo's code to initialize the random seed assumes that
> Fortran's "system_clock" and the "clock_gettime(CLOCK_MONOTONIC" it
> calls give a result where 0 is the beginning of the epoch (like on
> Linux/glibc) or the system start up (as Windows'
> GetTickCount/GetTickCount64). However, QueryPerformanceCounter
> (probably intrinsically, but at least as used by Cygwin) returns
> some time based on the startup time
> - and as the frequency seems to
> be slow such that the result is 0 or (nearly) the same number for
> the startup. Thus, the random_seed initialization doesn't work as
> expected on Cygwin/Windows.
> b) Newlib is broken. For clock_gettime, CLOCK_MONOTONIC is not
> implemented. But both CLOCK_MONOTONIC and even
> _POSIX_MONOTONIC_CLOCK (with value 200112L) are defined.
No, newlib is right. Look again. In libc/include/time.h
CLOCK_MONOTONIC is only defined if _POSIX_MONOTONIC_CLOCK is defined.
In libc/include/sys/features.h, _POSIX_MONOTONIC_CLOCK is only
defined for RTEMS and Cygwin.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple