Changes between Version 8 and Version 9 of Building/Unregisterised


Ignore:
Timestamp:
Feb 6, 2012 6:18:24 PM (2 years ago)
Author:
dterei
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Building/Unregisterised

    v8 v9  
    1  
    2  
    31= Unregisterised builds = 
    42 
    53Normally GHC will try to do a so-called registerised build, where it uses various architecture and OS specific knowledge to get more efficient code. However, on an architecture where this information has not been created, or has not been kept up-to-date, it is necessary to do an unregisterised build, which uses just plain old portable C. 
    64 
    7 To do an unregisterised build, add the following to your `mk/build.mk` file: 
     5To do an unregisterised build, remove the comment from the following line in your `mk/build.mk` file: 
    86 
    97{{{ 
    10 GhcUnregisterised=YES 
    11 GhcWithNativeCodeGen=NO 
    12 SplitObjs=NO 
     8# An unregisterised, optimised build of ghc, for porting: 
     9#BuildFlavour = unreg 
    1310}}} 
    1411 
    1512GHC will automatically do an unregisterised build on platforms that it knows don't currently have registerised support. 
    1613 
    17 Currently the native code generator requires a registerised build. Object splitting only works when building registerised. 
     14The various part of GHC work with registerised and unregisterised as follows: 
     15 
     16 * The native code generator requires a registerised build. 
     17 * Object splitting requires a registerised build. 
     18 * The C backend requires an unregisterised build. 
     19 * The LLVM backend works with either a registerised or unregisterised build.