Re: Parsing timestamps?

On Thu, 17 Jul 2025 12:41:45 +0000, Anton Ertl wrote:

mhx@iae.nl (mhx) writes:

Well, that is strange ...

[..]

The output should be the approximate number of seconds.  Here's what I
get from the cycle:u numbers for iForth 5.1-mini given in the earlier
postings:
>
\ ------------ input ---------- | output
 6_482_017_334 scale 7 5 3 f.rdp 1.07534 ok
 6_452_716_125 scale 7 5 3 f.rdp 1.07048 ok
 2_949_273_264 scale 7 5 3 f.rdp 0.48927 ok
14_634_786_781 scale 7 5 3 f.rdp 2.42785 ok
>
The resulting numbers are not very different from those you show.  My
measurements include iForth's startup overhead, which may be one
explanation why they are a little higher.

You are right, of course. I was confused by the original posting's
second table (which showed #instructions but was labeled #cycles).
 ( For the record, I used #7963 iterations of the code to get
   approximately 1 second runtime for the naive implementation. )
-marcel
--