Hello,

I wont to know the time that benchmark needs to run 200 benchmark on a 1 mhz 6502. So I can compare it with the time need with a 6502 emulator running fig-forth on a esp32.

Cheers,

Jan

Running a slightly hacked 6502 FIG FORTH on a 65816 simulator I get the following:


cc@ reads the simulator cycle counter as a double (limited to 24 bits on this setup).
Doing 200 benchmark runs far longer than the 16777216 cycles where cc@ wraps.

1081868 cycles at 1MHz would be 1.081868 secs.

_________________
http://WilsonMinesCo.com/ lots of 6502 resources
The "second front page" is http://wilsonminesco.com/links.html .
What's an additional VIA among friends, anyhow?

Here is a modified version of the benchmark code.
It includes a checksum to help verify the processing is correct.


I've fixed my cc@ so it returns 32 bits of cycle counter, so I can time longer runs.

Here are my results for various FORTHs:

FIG modified 8bit Indirect-Threaded -------------------
104 bytes
cc@ 200 benchmark cc@ d- d. 748 -1023891113 OK 1024 sec @ 1MHz
3000000003. 50003 u/ . . -5540 20015 OK

FIG modified 8bit Subroutine-Threaded --------------------
133 bytes
cc@ 200 benchmark cc@ d- d. 748 -382665927 OK 383 sec @ 1MHz
3000000003. 50003 um/mod . . -5540 20015 OK

FIG modified 16bit Indirect-Threaded -------------------
104 bytes
cc@ 200 benchmark cc@ d- d. 748 -485138841 OK 485 sec @ 1MHz
3000000003. 50003 u/ . . -5540 20015 OK

FIG modified 16bit Subroutine-Threaded -------------------
136 bytes
cc@ 200 benchmark cc@ d- d. 748 -192266443 OK 192 sec @ 1MHz
3000000003. 50003 u/ . . -5540 20015 OK

65816F 16bit Subroutine-Threaded ------------------
140 bytes
cc@ 200 benchmark cc@ d- d. 748 -117452133 ok 117 sec @ 1MHz
3000000003. 50003 um/mod . . -5540 20015 ok

Tali 8bit Subroutine-Threaded ---------------------
410 bytes
cc@ 200 benchmark cc@ d- d. 748 -369954558 ok 370 sec @ 1MHz
3000000003. 50003 um/mod . . -5540 20015 ok

GForth-fast on x64 --------------------
200 benchmark 748 ok
3000000003. 50003 um/mod . . 59996 20015 ok