Nope. Polymorphic Inline Caching. And why shouldn't JIT compilers use MMU "memory address violation exception" to check for end of range? Same for TLB.
I could flood you with hundreds of papers about that. I am using that all time. Of you were right and such knowledgeable, PicoLisp would run fast. But it doesn't. So take my pointers and - learn something new! ;-) Best regards, Guido Am Mittwoch, 22. April 2020 schrieb Alexander Burger <a...@software-lab.de>: > On Wed, Apr 22, 2020 at 03:49:41PM +0200, Guido Stepken wrote: >> Well, we have year 2020, not Dijksra 1978. Even embedded systems have a MMU >> and you get "Memory Access Violation", so no pointer rage checks needed to >> be handled by CPU any longer. > > Sigh, you don't understand at all how a Lisp interpreter works. > It is *all* type checks. We have dynamic data. Please stop > talking about things you have no clue of! > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
