This repo contains LLILC, an LLVM based compiler for .NET Core. It includes a set of cross-platform .NET code generation tools that enables compilation of MSIL byte code to LLVM supported platforms.

Перейти к файлу

Bengu Li d1d9ece652 Merge pull request #481 from libengu/ExcludeTestCMOV Exclude Directed\cmov test cases that have issues with LLILC		2015-04-21 17:03:35 -07:00
Documentation	Add GC Support Staging Plan	2015-04-21 14:03:14 -07:00
include	Handle merging of nativeint and unmanaged pointers as PHI operand types.	2015-04-20 17:04:13 -07:00
lib	Merge pull request #483 from erozenfeld/MDArrayFix	2015-04-21 17:02:57 -07:00
test	Exclude Directed\cmov test cases that have issues with LLILC	2015-04-21 12:00:32 -07:00
tools	Fix typo in Driver readme	2015-02-19 14:35:44 -08:00
utils	Remove mutually exclusive group	2015-03-23 14:06:04 -07:00
.clang-format	Reformat sources to be LLVM convention compliant	2015-03-11 13:02:04 -07:00
.gitattributes	Initial commit	2015-02-12 14:54:02 -08:00
.gitignore	Add __pycache__ to .gitignore	2015-04-16 12:52:19 -07:00
CMakeLists.txt	Correct main CMakeLists.txt file for standalone executables.	2015-04-20 13:29:43 -07:00
LICENSE.TXT	Initial commit	2015-02-12 14:54:02 -08:00
README.md	Added Gitter badge	2015-04-15 13:49:49 +00:00

README.md

Welcome to LLILC

Build Status

	Windows	Linux
Debug
Release

Introduction

LLILC is an LLVM based MSIL Compiler - we pronounce it 'lilac' - with a goal of producing a set of cross-platform .NET code generation tools. Today LLILC is being developed against dotnet/CoreCLR for use as a JIT, but an ahead of time (AOT) compiler is planned for the future.

See the wiki for more information. It has a more complete discussion of our background and goals as well as "getting started" details and developer information.

Supported Platforms

Our initial supported platform is Windows, but Linux and Mac OS X support are under development.

Contributions

LLILC is just starting up. Only a few tests are working and there are lots of places where we need help. Please see our issues or the contributing page for how to pitch in.