Sujet : Re: Performance benefits of primitive-centric code
De : anton (at) *nospam* mips.complang.tuwien.ac.at (Anton Ertl)
Groupes : comp.lang.forthDate : 13. Jun 2025, 07:49:18
Autres entêtes
Organisation : Institut fuer Computersprachen, Technische Universitaet Wien
Message-ID : <2025Jun13.084918@mips.complang.tuwien.ac.at>
References : 1 2 3 4 5 6 7
User-Agent : xrn 10.11
Paul Rubin <
no.email@nospam.invalid> writes:
minforth@gmx.net (minforth) writes:
It looks like the biggest improvement came from switching
to the benchark engine. What does that mean?
>
It means switching from the ITC interpreter to a faster one
(gforth-fast) that uses a mixture of DTC and native code generation, if
I have it right.
Already the second step "now switch to direct-threaded code" switches
to DTC (but not the debugging engine), and "+dynamic superinstructions
with replication" introduces the mixture of DTC and native code
generation. The switch to the benchmarking engine is the step after
that, and I explained it in another posting.
- anton
-- M. Anton Ertl http://www.complang.tuwien.ac.at/anton/home.htmlcomp.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/