(blog.reverberate.org)

122 points phsilva | 1 comments | 17 Feb 25 07:12 UTC | HN request time: 0.221s | source

Show context

riffraff ◴[20 Feb 25 06:44 UTC] No.43111815[source]▶

How does this differ from direct threading interpreters?

It seems like it solves the same problem (saving the function call overhead) and has the same downsides (requires non-standard compiler extensions)

EDIT: it seems the answer is that compilers do not play well with direct-threaded interpreters and they are able to perform more/better optimizations when looking at normal-sized functions rather than massive blocks

http://lua-users.org/lists/lua-l/2011-02/msg00742.html

replies(3): >>43112497 #>>43112649 #>>43116851 #

1. coldtea ◴[20 Feb 25 09:08 UTC] No.43112649[source]▶

>>43111815 #

>and has the same downsides (requires non-standard compiler extensions)

It's not a downside if:

(a) you have those non-standard compiler extensions in the platforms you target

↑

A tail calling interpreter for Python (already landed in CPython)