Update status #1075
Comments
I hope this is revised since even Azul is using LLVM for their next generation JVM, there is potential for .net. https://www.azul.com/called-new-jit-compiler-falcon/ |
just sames like https://github.com/Microsoft/LLVMSharp maybe we should go to wait kotlin native to support windows platform C# is hard to native in microsoft,all of natively project is dead. |
Seems like @sandreenko is working on the ObjectWriter branch: https://github.com/dotnet/llilc/tree/ObjectWriter |
There's a lot of work being done in [dotnet/corert](https://github.com/dotnet/corert] around native compilation, which is currently using RyuJIT as its AoT compiler but also has an "experimental" IL-to-C++-to-native compiler. That already works for simple console applications, building native self-contained executables for Windows and Linux (and possibly Mac, I haven't tried). So there are multiple possible reasons why this project might have gone quiet:
|
im not sure if CoreRT used in .net Core self-contained. where,im just think .net Core(1.1ver) self-contained. thats just created a .net program loader. |
Work on LLILC was undertaken to overtake/supersede LLVMSharp according to: https://dotnetfoundation.org/blog/2015/04/14/announcing-llilc-llvm-for-dotnet however, seems like LLILC is kaput, and LLVMSharp kicking... what's up? |
See https://github.com/dotnet/coreclr/issues/4331#issuecomment-313179155 -- in particular:
|
It looks like this project is dead (no commits since June 2016). It might be worth updating the README.md with this fact and possibly rationale.
The text was updated successfully, but these errors were encountered: