Re: Parsing timestamps?

Hans Bezemer <the.beez.speaks@gmail.com> writes:

I'm also puzzled why there is always so emphasis on the "speed" issue. I
mean - if you want speed, do your program in C -O3 so to say. It'll blow
any Forth out of the water.

Take a look at the bubble benchmark in Figure 1 of
<https://www.complang.tuwien.ac.at/papers/ertl24-interpreter-speed.pdf>.
SwiftForth, VFX, and Gforth with all optimizations (the baseline) are
faster than gcc-12 -O3.  The reason for that is:

|For bubble, gcc -O3 auto-vectorizes, and the result is that there is
|partial overlap between a store and a following load, which results
|in the hardware taking a slow path rather than performing one of its
|store-to-load forwarding optimizations.

- anton
--
M. Anton Ertl  http://www.complang.tuwien.ac.at/anton/home.html
comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html
     New standard: https://forth-standard.org/
EuroForth 2023 proceedings: http://www.euroforth.org/ef23/papers/
EuroForth 2024 proceedings: http://www.euroforth.org/ef24/papers/