[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: updating code in the jit context...
From: |
Aleksey Demakov |
Subject: |
Re: updating code in the jit context... |
Date: |
Wed, 20 May 2020 15:42:37 +0300 |
Hi,
Actually the ELF support in libjit was never completed. You are the
first person to actually ask for this feature.
Regards,
Aleksey
On Wed, May 20, 2020 at 3:04 PM kris <address@hidden> wrote:
>
> hello folks.
> I'm thrashing around for a way to run code and replace parts on the fly.
> I have this going in a bytecode environment but want to extend it to native.
> in general jitting looks to be the way and in particular libjit looks
> close - I think it's ELF handling
> means I can take the object files from an established compilation
> chain and add them all
> to a libjit context, then just invoke the entry point function.
> however, my aim is to implement a development cycle that creates new
> versions of those
> object files.
> for that I would need to be able to drop the memory allocated for a
> particular injected object
> file and for the new object file's symbols to overwrite existing one's
> in the symbol table (the order of reloading object files ensures no
> patching of existing in-memory code needed).
> unfortunately jit_readelf_add_to_context doesn't return any means of
> tracking the object
> so I guess there is no provision for unloading code.
> is that the case?
> if not, is there any technical reason that precludes it?
>
> thanks.
>