Changes between Version 9 and Version 10 of Commentary/Compiler/Backends/LLVM

Feb 25, 2010 3:05:15 AM (8 years ago)

Split content into multiple pages as I am adding more and single page wont work with the amount and variety


  • Commentary/Compiler/Backends/LLVM

    v9 v10  
    13 = Patches =
     13 * [wiki:Commentary/Compiler/Backends/LLVM/Installing Installing & Using]
     14 * [wiki:Commentary/Compiler/Backends/LLVM/Design Design & Implementation]
     15 * [wiki:Commentary/Compiler/Backends/LLVM/Issues Issues with the Back-end]
    15  * GHC Patch (applies to GHC):
    16  * LLVM Patch (applies to LLVM):
    18 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
    21 = Installing =
    23 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'.
    25 To build GHC you need to add two flags to, they are:
    27 {{{
    28 GhcWithLlvmCodeGen = YES
    29 GhcEnableTablesNextToCode = NO
    30 }}}
    32 The LLVM code generator doesn't support at this time the {{{TABLES_NEXT_TO_CODE}}} optimisation due to limitations with LLVM.
    34 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.
    36 LLVM is very easy to build and install. It can be done as follows:
    38 {{{
    39 $ svn co llvm
    40 $ cd llvm
    41 $ patch -p0 -i ~/llvm-ghc.patch
    42 $ ./configure --enable-optimized # probably also want to set --prefix
    43 $ make
    44 $ make install
    45 }}}
    47 Just make sure this modified version of LLVM is on your path and takes precedence over any other builds.
    50 = Using =
    52 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).
    54 {{{ghc --info}}} should also now report that it includes the llvm code generator.
    56 The [ ghc-core] tool also supports the llvm backend, and will display the generated assembly code for your platform.
    58 = Supported Platforms & Correctness =
    60  * 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).
    62  * 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.
    64  * 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.)
    67 = Performance =
    69 (All done on linux/x86-32)
    71 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:
    73 ||NCG || 1.11||
    74 ||C || 1.05||
    75 ||LLVM || 1.14||
    77 A nice demonstration of the improvements the LLVM back-end can bring to some code though can be see at
    79 = LLVM Back-end Design =
    82 The initial design tries to fit into GHC's current pipeline stages as seamlessly as possible. This allows for quicker development and focus on the core task of LLVM code generation.
    84 The LLVM pipeline works as follows:
    86   * New path for LLVM generation, separate from C and NCG. (path forks at compiler/main/CodeOutput.lhs, same place where C and NCG fork).
    87   * LLVM code generation will output LLVM assembly code.
    88   * The LLVM assembly code is translated to an object file as follows
    89      * First, there is an '!LlvmAs' phase which generates LLVM bitcode from LLVM assembly code (using the {{{llvm-as}}} tool).
    90      * The LLVM optimizer is run which is a series of bitcode to bitcode optimization passes (using the {{{llc}}} tool).
    91      * Finally an object file is created from the LLVM bitcode (using the {{{llc}}} tool)
    93   * This brings the LLVM path back to the other back-ends.
    94   * The final state is the Link stage, which uses the system linker as with the other back-ends.
    96 Here is a diagram of the pipeline:
    98 {{{
    99   Cmm -> (codeOutput) --->(ncg) Assembler                -->(mangler, splitter) --> ('As' phase) -----> Object Code --> (link) --> executable
    100                           \---> LLVM Assembler           --> LLVM Optimizer     --> ('llc' phase) -----/
    101 }}}
    103 This approach was the easiest and thus quickest way to initially implement the LLVM back-end. Now that it is working, there is some room for additional optimisations. A potential optimisation would be to add a new linker phase for LLVM. Instead of each module just being compiled to native object code ASAP, it would be better to keep them in the LLVM bitcode format and link all the modules together using the LLVM linker. This enable all of LLVM's link time optimisations. All the user program LLVM bitcode will then be compiled to a native object file and linked with the runtime using the native system linker.
    106 = Implementation Issues =
    108 == LLVM Changes ==
    110 The biggest problem is that LLVM doesn't provide all the features we need. The two issues below, 'Register Pinning' and 'TNTC' are the primary examples of this. While there is a patch for LLVM to partially correct fix this, this is a problem in itself as we now must include in GHC our own version of LLVM. Eventually we need to either get the changes we need included in LLVM or improve LLVM so that the features we require could be included dynamically.
    112 == Register Pinning ==
    114 The new back-end supports a custom calling convention to place the STG virtual registers into specific hardware registers. The current approach taken by the C back-end and NCG of having a fixed assignment of STG virtual registers to hardware registers for performance gains is not implemented in the LLVM back-end. Instead, it uses a custom calling convention to support something semantically equivalent to register pinning. The custom calling convention passes the first N variables in specific hardware registers, thus guaranteeing on all function entries that the STG virtual registers can be found in the expected hardware registers. This approach is believed to provide better performance than the register pinning used by NCG/C back-ends as it keeps the STG virtual registers mostly in hardware registers but allows the register allocator more flexibility and access to all machine registers.
    116 == TABLES_NEXT_TO_CODE ==
    118 GHC for heap objects places the info table (meta data) and the code adjacent to each other. That is, in memory, the object firstly has a head structure, which consists of a pointer to an info table and a payload structure. The pointer points to the bottom of the info table and the closures code is placed to be straight after the info table, so to jump to the code we can just jump one past the info table pointer. The other way to do this would be to have the info table contain a pointer to the closure code. However this would then require two jumps to get to the code instead of just one jump in the optimised layout. Achieving this layout can create some difficulty, the current back-ends handle it as follows:
    120   * The NCG can create this layout itself
    121   * The C code generator can't. So the [wiki:Commentary/EvilMangler Evil Mangler] rearranges the GCC assembly code to achieve the layout.
    123 There is a build option in GHC to use the unoptimised layout and instead use a pointer to the code in the info table. This layout can be enabled/disabled by using the compiler {{{#def TABLES_NEXT_TO_CODE}}}. As LLVM has no means to achieve the optimised layout and we don't wish to write an LLVM sister for the Evil Mangler, the LLVM back-end currently uses the unoptimised layout. This apparently incurs a performance penalty of 5% (source, Making a ''Fast Curry: Push/Enter vs. Eval/Apply for Higher-order Languages'', Simon Marlow and Simon Peyton Jones, 2004).
    125 == Shared Code with NCG ==
    127 It is probable that some of the code needed by the LLVM back-end is already implemented for the NCG back-end. Some examples of this code would be the following two functions in ''compiler/main/AsmCodeGen.lhs'':
    129   ''fixAssignsTop''::
    130     Changes assignments to global registers to instead assign to the !RegTable, used for non-pinned virtual registers.
    131   ''cmmToCmm''::
    132     Optimises the cmm code, in particular it changes loads from global registers to instead load from the !RegTable.
    134 == LLVM IR Representation ==
    136 The LLVM IR is modeled in GHC using an algebraic data type to represent the first order abstract syntax of the LLVM assembly code. The LLVM representation lives in the 'Llvm' subdirectory and also contains code for pretty printing. This is the same approach taken by [ EHC]'s LLVM Back-end, and we adapted the [ module] developed by them for this purpose.
    138 It is an open question as to if this binding should be split out into its own cabal package. Please contact the GHC mailing list if you think you might be a user of such a package.
    140 = Validate =
    142 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.
    144 '''Linux/x86-32:'''
    145 {{{
    146 OVERALL SUMMARY for test run started at Do 18. Feb 11:21:48 EST 2010
    147 2457 total tests, which gave rise to
    148 9738 test cases, of which
    149 0 caused framework failures
    150 7573 were skipped
    152 2088 expected passes
    153 76 expected failures
    154 0 unexpected passes
    155 1 unexpected failures
    157 Unexpected failures:
    158 user001(normal)
    159 }}}
    161 '''Linux/x86-64:'''
    163 {{{
    164 OVERALL SUMMARY for test run started at Thu 18 Feb 15:28:32 EST 2010
    165 2458 total tests, which gave rise to
    166 9739 test cases, of which
    167 0 caused framework failures
    168 7574 were skipped
    170 2087 expected passes
    171 77 expected failures
    172 0 unexpected passes
    173 1 unexpected failures
    175 Unexpected failures:
    176 T1969(normal)
    177 }}}
    179 '''Mac OS X 10.5/x86-32:'''
    181 {{{
    182 OVERALL SUMMARY for test run started at Thu Feb 18 12:35:49 EST 2010
    183 2458 total tests, which gave rise to
    184 9122 test cases, of which
    185 0 caused framework failures
    186 6959 were skipped
    188 2085 expected passes
    189 76 expected failures
    190 0 unexpected passes
    191 2 unexpected failures
    193 Unexpected failures:
    194 T1969(normal)
    195 ffi005(optc)
    196 }}}
    198 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.