[DGD] JIT compiler

[Raymond Jennings]

This seems to be most like runtime loadable kernel modules for linux.

Is that about the case?

Also, separately, will JIT compilation of LPC bytecode influence line
number information for the LPC source?


On Thu, Feb 21, 2019 at 7:08 AM <bart at wotf.org> wrote:

> Interesting development. Sadly I am very very low on time so can't really
> look
> at this in the near future, but I'm quite curious what this will do for my
> codebase.
>
> Bart.
>
> On Tue, 19 Feb 2019 22:53:27 +0100, Felix A. Croes wrote
> > Precompilation was dropped as a feature for DGD 1.5.  I want to
> > replace it with a JIT compiler in the near future.
> >
> > JIT compilation is going to be done through an extension module.  The
> > extension module will communicate with another program, and that
> > program will do the actual compilation of LPC bytecode to machine
> > code.  This way, DGD will be isolated from the JIT compiler, which
> > could crash or have memory leaks.  The same JIT compiler module
> > will also work for Hydra.
> >
> > The JIT compiler will produce object files (one for each LPC object)
> > which can be loaded at runtime into DGD's runtime process.  Since
> > they're saved as files, they can be cached and don't necessarily
> > have to be recompiled after DGD reboots.
> >
> > The current state of the JIT compiler is that basic block detection
> > is finished, and the value type produced by every VM instruction can
> > be determined.  This is sufficient for conversion to LLVM code.  I
> > currently don't have a lot of time to work on it, but the end is in
> > sight.
> >
> > I've pushed the current code to <https://github.com/dworkin/lpc-ext>.
> >
> > Regards,
> > Felix Croes
> > ____________________________________________
> > https://mail.dworkin.nl/mailman/listinfo/dgd
>
>
> --
> https://www.bartsplace.net/
> https://wotf.org/
> https://www.flickr.com/photos/mrobjective/
>
> ____________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd