Re: Managing the JIT

"BGB / cr88192" <cr88192@hotmail.com> a icrit dans le message de news:
> "Armel" <armelasselin@hotmail.com> wrote in message
>> "Philip Herron" <herron.philip@googlemail.com> a icrit dans le message de
>>> [...]
>>> something. I am having trouble finding more stuff on how this works
>>> would be great if you could point me in the right direction?! :)
>>
>> I just felt on the asmjit project : http://code.google.com/p/asmjit/
>> it seems that it does not contain megatons of code, you may find
>> interesting to read it.
>
> [...]
> OTOH, my assembler uses a textual interface (with a NASM / YASM style
> syntax).
> [...]


in fact, the function call based API could be considered as a lower
access level to the same JIT. inside your assembler with textual
interface, you probably already have this code, not providing it to
who needs it is just a loss.


by the way, one could well have the generation code behind each
function e.g. jit.move (ax, 25); generate either the binary or
assembler text for dump purposes. and the upper level interface could
understand this dumpped ASM and generate the calls!


i'd be personnally more likely to use a direct-to-binary JIT rather
than a textual interface (a JIT could be of interest to our ECMAScript
engine) but indeed a dump facility could really interest me as well,
though I see that as a debugging feature, not the corner stone of the
JIT engine.


Regards
Armel

Return to the comp.compilers page.
Search the comp.compilers archives again.