This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Cygwin with clock_gettime and CLOCK_MONOTONIC - gives always 0


Ciao Steve,

Il 12/04/2013 1.59, Steve Kargl ha scritto:
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

I DID that:

http://gcc.gnu.org/ml/fortran/2013-04/msg00033.html


It is only at the end of it that was opened the new on Cygwin:

http://cygwin.com/ml/cygwin/2013-04/msg00184.html


BTW, it contains also the link to the first... :)


Ciao,
  Angelo.



did not include actually inspecting what these two lines do:

    CALL SYSTEM_CLOCK(COUNT=clock)
    seed = clock + 37 * (/ (i-1), 1=1, n) /)

because your subject would have been "SYSTEM_CLOCK is broken
on cygwin".

If you want to see an actual issue with "Random seed initialization"
go read PR 52879.



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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]