Build libgccjit library as part of GCC port(s) or as separate port(s).

[kstephens (Kurt Stephens)]

libgccjit is a JIT API for embedding GCC compiler in a runtime.

It's an alternative to LLVM and libjit.

libccjit has been part of GCC trunk since GCC 5.

Building appears to be straightforward; ./configure options are documented in the references.

References:

• ​https://gcc.gnu.org/wiki/JIT
• ​https://gcc.gnu.org/onlinedocs/jit/

[ryandesign (Ryan Carsten Schmidt)]

Presumably we'd add these to the libgcc and libgcc-devel ports?

I see that docs say:

Note that libgccjit is currently of “Alpha” quality; the APIs are not yet set in stone, and they shouldn’t be used in production yet.

[kstephens (Kurt Stephens)]

If it's in trunk, is that good enough for libcc-devel? The caveat emptor is documented. Are there other GCC backends in trunk that are explicitly excluded? Maybe these are good reasons for a separate port dependent on the libgcc-devel port?

[dsedivec]

Should this be closed? It looks like (at least) gcc10 now includes libgccjit. See also #61130.

[wyuenho (Jimmy Yuen Ho Wong)]

No it shouldn't be closed. Emacs has just merged the native compilation branch into master, it would be nice if it could only depend a libgccjit port instead of the entirety of gcc and its dependencies.

[pmetzger (Perry E. Metzger)]

I'm not sure you can build gccemacs with just libgccjit and not the rest of gcc. Can you?

[mascguy (Christopher Nielsen)]

Adding Michael and Chris to the mix.