Path: ...!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.lang.fortran
Subject: Re: system_clock
Date: Mon, 4 Nov 2024 23:09:12 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 12
Message-ID: <vgbk6o$15jej$1@dont-email.me>
References: <vgbilt$152df$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 05 Nov 2024 00:09:12 +0100 (CET)
Injection-Info: dont-email.me; posting-host="87dc4f949347fc961291bbed2d24e27d";
	logging-data="1232339"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/C5ASlQ46SKb3Ia3m/vlj2"
User-Agent: Pan/0.160 (Toresk; )
Cancel-Lock: sha1:yYs3kIgKUV8rQm2wDIW6UngNmjk=
Bytes: 1349

On Mon, 4 Nov 2024 22:43:11 -0000 (UTC), Neil wrote:

> I have a question about the behaviour of system_clock.

The Fortran 2018 spec just says it returns a “processor-dependent value” 
which is “incremented by one for each clock count until the value 
COUNT_MAX is reached and is reset to zero at the next count”.

> Why is nvfortran so different?

This code is running on the GPU, right? That very likely does not maintain 
its own system clock.