|Version 9 (modified by 5 years ago) (diff),|
Normally 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.
To do an unregisterised build, remove the comment from the following line in your
# An unregisterised, optimised build of ghc, for porting: #BuildFlavour = unreg
GHC will automatically do an unregisterised build on platforms that it knows don't currently have registerised support.
The various part of GHC work with registerised and unregisterised as follows:
- The native code generator requires a registerised build.
- Object splitting requires a registerised build.
- The C backend requires an unregisterised build.
- The LLVM backend works with either a registerised or unregisterised build.