This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [Patch, fortran] PR 56919 SYSTEM_CLOCK on Windows
- From: Janne Blomqvist <blomqvist dot janne at gmail dot com>
- To: Tobias Burnus <burnus at net-b dot de>
- 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 15:54:56 +0300
- 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> <516BF7D6 dot 3010002 at net-b dot de>
On Mon, Apr 15, 2013 at 3:51 PM, Tobias Burnus <burnus@net-b.de> wrote:
> 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.
Indeed, thanks for spotting it, and fixing it quickly!
--
Janne Blomqvist