|Version 3 (modified by nathanhowell, 7 years ago) (diff)|
Installing & Using the LLVM Back-end
The patches needed can be found at:
- GHC Patch (applies to GHC): http://www.cse.unsw.edu.au/~davidt/downloads/ghc-llvmbackend-latest.patch
- LLVM Patch (applies to LLVM): http://www.cse.unsw.edu.au/~davidt/downloads/llvm-ghc.patch
These are the patches that you should be working with, they are 'stable'. The back-end also lives in a Git repository where the actual development work is done, this can be found at https://cgi.cse.unsw.edu.au/~davidt/cgit/cgit.cgi/Thesis%20GHC%20Dev/
Apply the darcs patch linked above to GHC head. This will make some changes across GHC, with the bulk of the new code ending up in 'compiler/llvmGen'.
To build GHC you need to add two flags to build.mk, they are:
GhcWithLlvmCodeGen = YES GhcEnableTablesNextToCode = NO
The LLVM code generator doesn't support at this time the TABLES_NEXT_TO_CODE optimisation due to limitations with LLVM.
You will also need LLVM installed on your computer to use the back-end. Version 2.6 or SVN trunk is supported. If you want to use the back-end in an unregistered ghc build, then you can use a vanilla build of LLVM. However if you want to use a registered GHC build (very likely) then you need to patch LLVM for this to work using the patch provided above.
LLVM is very easy to build and install. It can be done as follows:
$ svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm $ cd llvm $ patch -p0 -i ~/llvm-ghc.patch $ ./configure --enable-optimized # probably also want to set --prefix $ make $ make install
Just make sure this modified version of LLVM is on your path and takes precedence over any other builds.
Once GHC is built, you can trigger GHC to use the LLVM back-end with the -fllvm flag. There is also a new -ddump-llvm which will dump out the LLVM IR code generated (must be used in combination with the -fllvm flag. (or use the -keep-tmp-files flag).
ghc --info should also now report that it includes the llvm code generator.
The ghc-core tool also supports the llvm backend, and will display the generated assembly code for your platform.
Supported Platforms & Correctness
- Linux x86-32/x86-64 are currently well supported. The back-end can pass the test suite and build a working version of GHC (bootstrap test).
- Mac OS X 10.5 currently has a rather nasty bug with any dynamic lib calls (all libffi stuff) [due to the stack not being 16byte aligned when the calls are made as required by OSX ABI for the curious]. Test suite passes except for most the ffi tests.
- Other platforms haven't been tested at all. As using the back-end with a registered build of GHC requires a modified version of LLVM, people wanting to try it out on those platforms will need to either make the needed changes to LLVM themselves, or use an unregistered build of GHC which will work with a vanilla install of LLVM. (A patch for LLVM for x86 is linked to below.)
(All done on linux/x86-32)
A quick summary of the results are that for the 'nofib' benchmark suite, the LLVM code generator was 3.8% slower than the NCG (the C code generator was 6.9% slower than the NCG). The DPH project includes a benchmark suite which I (David Terei) also ran and for this type of code using the LLVM back-end shortened the runtime by an average of 25% compared to the NCG. Also, while not included in my thesis paper as I ran out of time, I did do some benchmarking with the 'nobench' benchmark suite. It gave performance ratios for the back-ends of around:
A nice demonstration of the improvements the LLVM back-end can bring to some code though can be see at http://donsbot.wordpress.com/2010/02/21/smoking-fast-haskell-code-using-ghcs-new-llvm-codegen/
The GHC patch has been validated to make sure it won't break anything. This is just compiling and running GHC normally but with the LLVM back-end code included. It doesn't actually test the LLVM code generator, just makes sure it hasn't broken the NCG or C code generator.
OVERALL SUMMARY for test run started at Do 18. Feb 11:21:48 EST 2010 2457 total tests, which gave rise to 9738 test cases, of which 0 caused framework failures 7573 were skipped 2088 expected passes 76 expected failures 0 unexpected passes 1 unexpected failures Unexpected failures: user001(normal)
OVERALL SUMMARY for test run started at Thu 18 Feb 15:28:32 EST 2010 2458 total tests, which gave rise to 9739 test cases, of which 0 caused framework failures 7574 were skipped 2087 expected passes 77 expected failures 0 unexpected passes 1 unexpected failures Unexpected failures: T1969(normal)
Mac OS X 10.5/x86-32:
OVERALL SUMMARY for test run started at Thu Feb 18 12:35:49 EST 2010 2458 total tests, which gave rise to 9122 test cases, of which 0 caused framework failures 6959 were skipped 2085 expected passes 76 expected failures 0 unexpected passes 2 unexpected failures Unexpected failures: T1969(normal) ffi005(optc)
All of the test failures fail for me with a unmodified GHC head build as well as when the LLVM patch is included, so the llvm patch isn't introducing any new failures.