-
Notifications
You must be signed in to change notification settings - Fork 11
Description
Is your feature request related to a problem? Please describe.
LLVM JIT is undergoing another major re-work (LLVM 13 has settled down and exposed more of ORCJitv2 in the "stable" C API, but there have been others as well and the stability is a matter of interpretation. Additionally not all of the consumers of LLVM.NET need JIT support. Thus, this proposal is to split the JIT managed layer to a distinct NUGET package so that it can evolve independently and track the progress of ORCJitv2 without impacting consumers of Llvm.NET in general.
Describe the solution you'd like
Distinct package for the managed code layer of the JJIT support (Already a distinct namespace so this shouldn't be a large scale effort.
Describe alternatives you've considered
- Leaving it as-is, worts and all.
- Dropping support for JIT outright as it's not a very stable feature of LLVM...
- Irony of this state is that LLVM was originally invented as a generalized framework for building JIT engines.