This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Patch, fortran] PR 56919 SYSTEM_CLOCK on Windows
- From: Tobias Burnus <burnus at net-b dot de>
- To: Janne Blomqvist <blomqvist dot janne at gmail dot com>
- Cc: Fortran List <fortran at gcc dot gnu dot org>, gcc patches <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 15 Apr 2013 14:51:34 +0200
- Subject: Re: [Patch, fortran] PR 56919 SYSTEM_CLOCK on Windows
- References: <CAO9iq9FBmgY8A9b7PXKAbcXhHKuMk8mk_cYAgo_mcP2yCcXUyw at mail dot gmail dot com> <51688469 dot 4060000 at net-b dot de> <CAO9iq9HTfRn3Pa3se9Ntois7gMywkUav9ydVfPQLjARCY7Qnzg at mail dot gmail dot com> <516BBC5F dot 10807 at net-b dot de> <CAO9iq9E---2bVE_mH-5PfFjTV=MgxFnUf9JanCELHkfiD+G5oA at mail dot gmail dot com>
Janne Blomqvist wrote:
I committed the attached patch with most of your suggestions as r197968.
Thanks! Although, I assume you meant "kind=8" in the last sentence:
+the underlying platform clock. @var{COUNT_MAX} usually equals
+@code{HUGE(COUNT_MAX)}. Note that the millisecond resolution of the
+@var{kind=4} version implies that the @var{COUNT} will wrap around in
+roughly 25 days. In order to avoid issues with the wrap around and for
+more precise timing, please use the @var{kind=4} version.
Hence, I committed the attached patch as obvious.
Tobias
Index: gcc/fortran/ChangeLog
===================================================================
--- gcc/fortran/ChangeLog (Revision 197969)
+++ gcc/fortran/ChangeLog (Arbeitskopie)
@@ -1,3 +1,7 @@
+2013-04-15 Tobias Burnus <burnus@net-b.de>
+
+ * intrinsic.texi (SYSTEM_CLOCK): Recommend kind=8.
+
2013-04-15 Janne Blomqvist <jb@gcc.gnu.org>
PR fortran/56919
Index: gcc/fortran/intrinsic.texi
===================================================================
--- gcc/fortran/intrinsic.texi (Revision 197969)
+++ gcc/fortran/intrinsic.texi (Arbeitskopie)
@@ -12052,7 +12052,7 @@
@code{HUGE(COUNT_MAX)}. Note that the millisecond resolution of the
@var{kind=4} version implies that the @var{COUNT} will wrap around in
roughly 25 days. In order to avoid issues with the wrap around and for
-more precise timing, please use the @var{kind=4} version.
+more precise timing, please use the @var{kind=8} version.
If there is no clock, or querying the clock fails, @var{COUNT} is set
to @code{-HUGE(COUNT)}, and @var{COUNT_RATE} and @var{COUNT_MAX} are