> -----Original Message----- > From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of David > Malcolm > Sent: 09 October 2013 22:32 > To: gcc@gcc.gnu.org > Subject: libgccjit.so: an embeddable JIT-compilation library based on GCC > > As some may have seen I posted a patch to gcc-patches that adds a way to > embed GCC as a shared library, for Just-In-Time compilation, for use > e.g. by bytecode interpreters: > http://gcc.gnu.org/ml/gcc-patches/2013-10/msg00228.html > > I've gone ahead and created a git-only on the mirror as branch > "dmalcolm/jit": > http://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/heads/dmalcolm/jit > and I've been committing patches there. > > I plan to post some of the patches for review against trunk (am > bootstrapping/regtesting them as I write). > > An example of using it can be seen at: > https://github.com/davidmalcolm/jittest/blob/master/README.rst > > Some questions for the GCC steering committee: > > * is this JIT work a good thing? (I think so, obviously, but can I go > ahead and e.g. add it to the wiki under "Current Projects"?) > > [snip]
I am not the committee but the JIT works is useful, awesome and I am pretty confident it will have quite a few users. Thank you so much for it.