Re: Assembler Interface of LuaJIT VM.

[neha mahajan <mahajan.neha.jal@...>]

Thanks Erik,

but I wanted to know why the implementation of ASM functions are in .dasc file, means we can implement the same in c with inline assembly functions. Then why this complex encoding engine[Dynasm] with its input source file.

On Wed, Sep 1, 2010 at 10:08 PM, Erik Lindroos <gliptic@gmail.com> wrote:

Hi,

I'm not Mike Pall, but I can tell you that the source to the interpreter (which becomes lj_vm.obj) is in buildvm_x86.dasc in the form of DynASM source. The functions mentioned simply implement different forms of function calls and are used by, for example, the similarly named Lua API functions.

/Erik

On Wed, Sep 1, 2010 at 1:34 PM, neha mahajan <mahajan.neha.jal@gmail.com> wrote:

Dear Sir,

we are very much impressed by the performance of LuaJIT.

 

we was going through the code, but we are unable to understand the assembler interface of vm i.e. lj_vm.s. we are unable to understand the basic functionality of this file so could you please through some light on these functions like lj_vm_pcall, lj_vm_cpcall, lj_vm_call etc.

 

we have already disassemble the lj_vm.s, but its corresponding pseudo code or logic functionality of these assembly functions are still missing.

your suggestion will be quite helpful.

Thanks,
Neha.

-- 
Neha Mahajan.