зеркало из https://github.com/dotnet/llilc.git
34df455822
This is a major change to runtest and checkdiff. First, it is changed to user pre-created baseline. Instead of huge LLVM IR baseline stored in GitHub that caused issues. Second, summary comparison is introduced. With one line per method, the runtest and checkdiff process is much more swift with summary only than previous approach. No dump runtest is also provided. Verbose dump functionality is still there. A normalization speed improvement is expected after this change. Third, LLVM IR dump level is introduced into LLILCJit. Right now it read env var directly. It will be updated when CLR Config is supported in LLILCJit. A GitHub wiki page is created to illustrate the usage. https://github.com/dotnet/llilc/wiki/Dev-Env-and-Test-Harness Below are Typical use cases: Developer Usage 1.Update your master to latest master 2.Build your baseline JIT: BuildAll or Build 3.Create a summary baseline: RunTest -Jit baseline-jit -Result SummaryBase -Dump Summary 4.Create a verbose baseline: RunTest -Jit baseline-jit -Result VerboseBase -Dump Verbose 5.Create your own branch 6.Do the new development or fix issues 7.Build your new JIT: Build 8.RunTest -Jit new-jit If failed with overall pass/failure and no dump, back to step 6 for fixing. 9.RunTest -Jit new-jit -Result SummaryDiff -Dump Summary 10.CheckDiff -Base SummaryBase -Diff SummaryDiff -Summary -UseDiffTool If failed with summary, find out which method is a new failure, back to step 6 for fixing. 11.RunTest -Jit new-jit -Result VerboseDiff -Dump Verbose 12.CheckDiff -Base VerboseBase -Diff VerboseDiff -UseDiffTool If any LLVM IR diff is not benign, back to step 6 for fixing. 13.Ready for a pull request. Lab PR Usage RunTest Lab PR usage is most simplified version. It only checks for overall pass/fail and does not keep any result. Lab Nightly Usage 1.RunTest -Jit last-known-good-jit -Result SummaryBase -Dump Summary or a summary result of running last-know-good-jit is kept in SummaryBase 2.RunTest -Jit latest-jit -Result SummaryDiff -Dump Summary 3.CheckDiff -Base SummaryBase -Diff SummaryDiff -Summary 4.If CheckDiff result is zero, mark latest-jit as last-known-good-jit. Result SummaryDiff could be kept as SummaryBase. 5.If CheckDiff result is not zero, send out failure notice to branch owner. Branch owner should analyze the case and bring relevant developer for fixing. |
||
|---|---|---|
| Documentation | ||
| include | ||
| lib | ||
| test | ||
| tools | ||
| utils | ||
| .clang-format | ||
| .gitattributes | ||
| .gitignore | ||
| CMakeLists.txt | ||
| LICENSE.TXT | ||
| README.md | ||
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 OSX 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.