Re: [TCLCORE] Bytecode compiler and monotonic time

[Arjen M. <Arj...@de...>]

Hi Christian,

The explanation of that absolute time seems to be this text (taken from Tcl 8.6, as that was the easiest for me 😉):

Every interpreter has two kinds of resource limits that may be imposed by any master interpreter upon its slaves. Command limits (of type command) restrict the total number of Tcl commands that may be executed by an interpreter (as can be inspected via the info cmdcount command), and time limits (of type time) place a limit by which execution within the interpreter must complete. Note that time limits are expressed as absolute times (as in clock seconds) and not relative times (as in after) because they may be modified after creation.
When a limit is exceeded for an interpreter, first any handler callbacks defined by master interpreters are called. If those callbacks increase or remove the limit,

(Paragpaph from RESOURCE LIMITS)

Regards,

Arjen

-----Original Message-----
From: Christian Werner <Chr...@t-...>
Sent: woensdag 14 mei 2025 09:03
To: tcl...@li...
Subject: Re: [TCLCORE] Bytecode compiler and monotonic time

Caution: This message was sent from outside of Deltares. Please do not click links or open attachments unless you recognize the source of this email and know the content is safe. Please report all suspicious emails to "Ser...@de..." as an attachment.


On 05/14/2025 08:39 AM, Harald Oehlmann wrote:

> ...
> Are you speaking about the modifications in generic/tclInterp.c in the bug branch ?
> https://core/
> .tcl-lang.org%2Ftcl%2Ftimeline%3Fr%3Dtkt3328635-posix-monotonic-clock%
> 26c%3D2025-05-14%2B06%253A30%253A15&data=05%7C02%7Carjen.markus%40delt
> ares.nl%7C7757c6162a59424519a408dd92b56b9c%7C15f3fe0ed7124981bc7cfe949
> af215bb%7C0%7C0%7C638828030079849378%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0e
> U1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld
> UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=RHvOcEUT6JGQ77Iq6bVDfjSBQ2m8YA6a6qIjq
> KndzQM%3D&reserved=0
>
> You can also see it in this diff:
> https://core/
> .tcl-lang.org%2Ftcl%2Finfo%2F8ea9c4081c39b8bf&data=05%7C02%7Carjen.mar
> kus%40deltares.nl%7C7757c6162a59424519a408dd92b56b9c%7C15f3fe0ed712498
> 1bc7cfe949af215bb%7C0%7C0%7C638828030079877245%7CUnknown%7CTWFpbGZsb3d
> 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiT
> WFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=dXKkQgsGa0XDZgn79zhNNd%2FMz
> vRCPMgEiGSJVfOx8CQ%3D&reserved=0
>
> When I look to "interp limit" man page, there, the limit is documented as milliseconds and seconds, and not as a fix time.
>
> So, this is a bug and not a design change?
>
> I see the usage of the monotonic clock in the branch for the following commands:
>
> - interpreter limit
> - time
> - after
>
> For me, all those are documented in time difference (e.g. monotonic clock) and not in wall clock difference.
> So, the delay/speedup by a wall clock change is IMHO a bug and not a documented feature.

Please read the "RESOURCE LIMITS" section in interp.n carefully especially for the description of the "-seconds" option.

For me as non native speaker the description sounds misleading but in fact that "-seconds" option is an absolute time in wall clock units.

BR,
Christian



_______________________________________________
Tcl-Core mailing list
Tcl...@li...
https://lists.sourceforge.net/lists/listinfo/tcl-core
DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.