# LLILC at Six Months - a Retrospective
October 2015
Back in April we announced LLILC,
an open-source [CoreCLR](https://github.com/dotnet/coreclr) compatible JIT
based on [LLVM](http://llvm.org). Since then we�ve been
hard at work on LLILC, and most of the core code generation is implemented.
LLILC is able to pass thousands of test cases on Windows and Linux, can pre-jit
(NGEN) anything it can jit, and can successfully jit the
[Roslyn](https://github.com/dotnet/roslyn) compiler compiling itself.
Our experiences with LLVM both as a code base and a community
continue to impress and inspire us. Work continues on both EH and GC, and
while we�ve made great progress on both fronts, and benefited from valuable
cross-industry collaboration, there is much still to do. The CoreCLR�s
requirements continue to push both us and LLVM into interesting new directions.
This document touches on our progress to date, and the challenges that remain.
## Background
This file has been truncated. show original
Could some of you experts give some of us mortals an overview on what llilc means to us with regards to netmf and the big IOT in general?
Will we be using this code base in the future? Will it replace netmf?
Thank you.
Could some of you experts give some of us mortals an overview on what llilc means to us with regards to IOT development?
Will we be using this code base in the future?
LLILC is not LLILUM, which is the native-AOT compiler proof-of-concept for NETMF.
@ godefroi - Got it, that was what I was thinking about. Thanks for the correction.
@ andre.m - Thanks for your clarification.