> Having multiple code generators is not mutually exclusive, and this effort does not mean MSFT is ditching any existing AOT (or for that matter JIT) compiler projects.
Of course not. But why spread your effort across two projects that duplicate functionality when you could focus on one?
Q: How does LLILC relate to the .NET Native work?
A: .NET Native provides a broad tool-chain, targeting Windows. The LLILC AOT could be used as the compiler component of .NET Native to target other platforms.
Since LLVM can run on Windows, you could also use it as your AOT compiler for multiple platforms (including Windows) once LLILC gets there.
Of course not. But why spread your effort across two projects that duplicate functionality when you could focus on one?