[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: LuaJIT - Trace aborted again
- From: Mike Pall <mikelu-1107@...>
- Date: Wed, 27 Jul 2011 12:04:52 +0200
Benjamin Segovia wrote:
> Note that HotPathVM paper:
>
> really makes me understand how Luajit works in a high-level
> perspective. (Mike, correct me if I am wrong, but the overall design
> is close to this paper, right?)
Ok, so it's a trace compiler and hotspot detection is done with
an interpreter. But that's how most JIT trace-compilers work.
Everything else is quite different.
Sorry, but there's no comprehensive summary of LuaJIT's design.
I guess you'll have to read the source and/or my older postings
to the list and elsewhere.
--Mike
- References:
- Re: LuaJIT - Trace aborted again, David Kastrup
- Re: LuaJIT - Trace aborted again, Mike Pall
- Re: LuaJIT - Trace aborted again, Benjamin Segovia
- Re: LuaJIT - Trace aborted again, Benjamin Segovia
- Re: LuaJIT - Trace aborted again, Benjamin Segovia
- Re: LuaJIT - Trace aborted again, Mike Pall
- Re: LuaJIT - Trace aborted again, Dirk Laurie
- Re: LuaJIT - Trace aborted again, Alex Bradbury
- Re: LuaJIT - Trace aborted again, Miles Bader
- Re: LuaJIT - Trace aborted again, Benjamin Segovia