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: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: Angelo Graziosi <angelo dot graziosi at alice dot it>
- Cc: Cygwin <cygwin at cygwin dot com>, fortran <fortran at gcc dot gnu dot org>
- Date: Thu, 11 Apr 2013 16:59:12 -0700
- Subject: Re: Cygwin with clock_gettime and CLOCK_MONOTONIC - gives always 0
- References: <51674473 dot 3030704 at alice dot it>
On Fri, Apr 12, 2013 at 01:17:07AM +0200, Angelo Graziosi wrote:
> Steve Kargl wrote
> > My
> > disagreemnet is predicated on the stupidity of using a 10 line
> > example subroutine without actually inspecting what it does on
> > whatever OS that one chooses to use.
> It is just because one has tested that code that these problems came to
> light... :-)
When testing, it would help if the results were properly
represented as your initial subject line was "Random seed
initialization". It seems clear to at least me your testing
did not include actually inspecting what these two lines do:
seed = clock + 37 * (/ (i-1), 1=1, n) /)
because your subject would have been "SYSTEM_CLOCK is broken
If you want to see an actual issue with "Random seed initialization"
go read PR 52879.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple