"For those who doesn't know about the project, the LuaJIT Language Toolkit is an implementation of the Lua programming language written in Lua iself. It works by generating a LuaJIT's bytecode including the debug informations and use the LuaJIT's virtual machine to run the generated bytecode."
This is like a Christmas present. I needed this tool badly enough that I've been reading the LuaJIT source code and mulling over just what it would take to write it.
I love the idea of this project, but as even Mike Pall has mentioned the "proper" way to do this is to target Lua code directly. LuaJIT is designed to speedup Lua, not LJ bytecode.
Where someone else http://rtsisyk.github.io/luafun/intro.html attempts to generate LuaJIT bytecode directly and tracing JIT doesn't speedup their code because LuaJIT isn't designed to speedup arbitrary bytecode but bytecode generated by the LuaJIT compiler.
There was still a more specific post that I am unable to locate where Mike specifically warned against targeting LuaJIT bytecode. I'd probably just post a message on the luajit list if you want clarification.
Just checked out your github page, you are like my brother from another mother. If I am in Berkeley I will drop you a line and we can code on some Forth JITs in Lua.
If that is true, you should ask your son to do some sort of write up on what he has learned. Anyone with serious technical skill but not the overhead of worrying about what they 'should' know is great to read. There are a lot of insights from someone without the cruft of conventional wisdom.
"For those who doesn't know about the project, the LuaJIT Language Toolkit is an implementation of the Lua programming language written in Lua iself. It works by generating a LuaJIT's bytecode including the debug informations and use the LuaJIT's virtual machine to run the generated bytecode."