Re: [Pnet-developers] libjit - separation of interfaces

[Rhys Weatherley]

On Thursday 03 June 2004 06:11 pm, Miroslaw Dobrzanski-Neumann wrote:

> int jit_insn_pop_stack(jit_function_t func, jit_nint num_items)

You might be right about this one, but the block API is part of the three 
address system that libjit exposes to the front end.

> Have the frontend to know that libjit works with basic blocks?
> What if I decide to imitate the libjit implementing required frontend
> interfaces - am I forced to read "Aho et. all" prior to do that because
> dpas interpreter wants to use jit_block_current_is_dead ().

So, you want to throw away all of libjit and implement something completely 
different from scratch that has the same API?  Why not just modify libjit to 
include whatever optimisations you are interested in and leave the bulk of 
the framework intact?  If the framework has deficiences for your purposes, 
they can be addressed.

> In my opinion jit-block.h does not belong to public frontend interface
> because it presents the internal implementation details

By that rule, the whole of jit-insn.h is internal implementation detail, 
because the API is predicated on front end treating it like a three address 
system.  Other representations will need other API's.  Without jit-insn.h, 
there is no JIT at all.

Cheers,

Rhys.