Re: Emacs Lisp JIT Compiler

[Daniel Colascione]

> Paul> This sounds very interesting. I assume you'd publish it first on a
> Paul> branch so that we could look at it?
>
> Now it is feature/libjit.
>
> Paul> libjit has only one committer, Aleksey, and no commits since March.
> Is
> Paul> there a bottleneck there?
>
> Another possibility is to switch to gcc-jit.  On the up side, it is part
> of GCC, so it is maintained and widely ported.  The down side is that,
> currently, it requires more capabilities at runtime; for example it
> invokes the assembler and, I believe, uses dlopen under the hood.

I still think that needing binutils for ordinary use is a non-starter.

>
> One thing I've been thinking about with gcc-jit is that it would be
> "relatively" straightforward to also have it work as an ahead-of-time
> compiler.  What I picture here is a step during dumping where all the
> dumped bytecode functions are compiled into a shared library.
>
> It might be worth doing the experiment to find out.

In the end, it might be useful to adopt an SBCL-like compiled-code-only
model.