[Bug fortran/37832] System_Clock

2008-11-09 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2008-11-09 18:18 --- After doing some more testing and comparing g77 vs gfortran, gfortran actually provides higher resolution 1000 ticks/sec then g77 100 ticks/second on at least my platform (x86-64-linux) On Cygwin, results are iden

[Bug fortran/37832] System_Clock

2008-11-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2008-11-09 07:46 --- According to the g77 documentation, system_clock uses the times(2) function. gfortran uses either the time(2) (note no 's' on the end of the name) or the gettimeofday function. When I revise the gfortran routine

[Bug fortran/37832] System_Clock

2008-11-02 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2008-11-03 02:17 --- I will add this to my list and see if we can get to what g77 does. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added -

[Bug fortran/37832] System_Clock

2008-10-14 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2008-10-15 06:33 --- See also PR 28484 comment 5. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37832

[Bug fortran/37832] System_Clock

2008-10-14 Thread kargl at gcc dot gnu dot org
--- Comment #1 from kargl at gcc dot gnu dot org 2008-10-15 05:50 --- You can already get an integer(8) result. integer(8) ticks,rate call system_clock(count=ticks,count_rate=rate) print *, ticks, rate end gfc -o z a.f90 ./z 2131173368 1000 count_rate is det