Version 24 (modified by guest, 12 years ago) (diff)


Compiling one module: HscMain

Here we are going to look at the compilation of a single module. There is a picture that goes with this description, which appears at the bottom of this page, but you'll probably find it easier to open this link in another window, so you can see it at the same time as reading the text.

Look at the picture first. The yellow boxes are compiler passes, while the blue stuff on the left gives the data type that moves from one phase to the next. The entire pipeline for a single module is run by a module called HscMain (in compiler/main/HscMain). Here are the steps it goes through:

  • The program is initially parsed into the big HsSyn type. HsSyn is parameterised over the types of the term variables it contains. The first three passes (the front end) of the compiler work like this:

    • The parser produces HsSyn parameterised by RdrName. To a first approximation, a RdrName is just a string.

    • The renamer transforms this to HsSyn parameterised by Name. To a first appoximation, a Name is a string plus a Unique (number) that uniquely identifies it. In particular, the renamer associates each identifier with its binding instance and ensures that all occurrences which associate to the same binding instance share a single Unique.

    • The typechecker transforms this further, to HsSyn parameterised by Id. To a first approximation, an Id is a Name plus a type. In addition, the type-checker converts class declarations to Classes, and type declarations to TyCons and DataCons. And of course, the type-checker deals in Types and TyVars. The data types for these entities (Type, TyCon, Class, Id, TyVar) are pervasive throughout the rest of the compiler.

These three passes can all discover programmer errors, which are sorted and reported to the user.

  • The desugarer (compiler/deSugar/Desugar) converts from the massive HsSyn type to GHC's intermediate language, CoreSyn. This Core-language data type is unusually tiny: just eight constructors.

    This late desugaring is somewhat unusual. It is much more common to desugar the program before typechecking, or renaming, becuase that presents the renamer and typechecker with a much smaller language to deal with. However, GHC's organisation means that
    • error messages can display precisely the syntax that the user wrote; and
    • desugaring is not required to preserve type-inference properties.
    Generally speaking, the desugarer produces user errors or warnings. But it does produce some. In particular, (a) pattern-match overlap warnings are produced here; and (b) when desugaring Template Haskell code quotations, the desugarer may find that THSyntax is not expressive enough. In that case, we must produce an error (compiler/deSugar/DsMeta).
  • Then the CoreTidy pass gets the code into a form in which it can be imported into subsequent modules (when using --make) and/or put into an interface file. There are good notes at the top of the file compiler/main/TidyPgm.lhs; the main function is tidyProgram, for some reason documented as "Plan B".

The serialisation does (pretty much) nothing except serialise. All the intelligence is in the Core-to-IfaceSyn conversion; or, rather, in the reverse of that step.

  • The same, tidied Core program is now fed to the Back End. First there is a two-stage conversion from CoreSyn to StgSyn.
    • The first step is called CorePrep, a Core-to-Core pass that puts the program into A-normal form (ANF). In ANF, the argument of every application is a variable or literal; more complicated arguments are let-bound. Actually CorePrep does quite a bit more: there is a detailed list at the top of the file compiler/coreSyn/CorePrep.lhs.
    • The second step, CoreToStg, moves to the StgSyn data type (the code is in [GhcFile(stgSyn/CoreToStg.lhs)?]. The output of CorePrep is carefully arranged to exactly match what StgSyn allows (notably ANF), so there is very little work to do. However, StgSyn is decorated with lots of redundant information (free variables, let-no-escape indicators), which is generated on-the-fly by CoreToStg.
  • Next, the code generator converts the STG program to a C-- program. The code generator is a Big Mother, and lives in directory compiler/codeGen
  • Now the path forks again:
    • If we are generating GHC's stylised C code, we can just pretty-print the C-- code as stylised C (compiler/cmm/PprC.hs)
    • If we are generating native code, we invoke the native code generator. This is another Big Mother, and lives in compiler/nativeGen.

The Diagram

This diagram is also located here, so that you can open it in a separate window.

Attachments (2)

Download all attachments as: .zip