Changes between Version 2 and Version 3 of Building/Preparation/RaspberryPi

Timestamp:

01/30/13 02:03:43 (4 months ago)

Author:

simonmar

Comment:

--

Building/Preparation/RaspberryPi

@@ -20 +20 @@
 }}}
 
-You can also build registerised: leave out the `--enable-unregisterised` option, but then you '''must''' use LLVM (see below).
+You can also build registerised: leave out the `--enable-unregisterised` option, but then you '''must''' install a suitable LLVM (see below).
 
 You'll need to use `integer-simple`, because the cross-compilation environment doesn't include GMP (see [wiki:Building/CrossCompiling]).
@@ -28 +28 @@
 == Using LLVM ==
 
- * When unregisterised, the C backend will be used by default, but you can optionally use LLVM.  Code generated using LLVM is compatible with code generated using the C backend.
- * When registerised, you ''must'' use LLVM.  The `-fllvm` option is unnecessary in this case.
+Note that LLVM 2.9 does not work for registerised code generation on ARM (it crashes), and LLVM 3.1 has been reported to generate incorrect code.  Success has been reported with LLVM 3.0 and 3.2.
 
-To use LLVM, add these to your `mk/build.mk`:
+ * When '''unregisterised''', the C backend will be used by default, but you can optionally use LLVM (see below).  Code generated using LLVM is compatible with code generated using the C backend.
+ * When '''registerised''', LLVM is the only backend that supports registerised compilation on ARM, so it will be used automatically.  You don't have to do anything except ensure that a suitable version of LLVM is installed.
+
+To use LLVM when unregisterised, add these to your `mk/build.mk`:
 
 {{{
-GhcLibHcOpts       = -O -fllvm -optlc -mtriple=arm-linux-gnueabihf -optlc -mattr=+vfp2 -optlc -float-abi=hard
-GhcRtsHcOpts      += -fllvm -optlc -mtriple=arm-linux-gnueabihf -optlc -mattr=+vfp2 -optlc -float-abi=hard
+GhcLibHcOpts       = -O -fllvm
+GhcRtsHcOpts      += -fllvm
 }}}
-
-Note that LLVM 2.9 does not work for registerised code generation on ARM (it crashes), and LLVM 3.1 has been reported to generate incorrect code.  Success has been reported with LLVM 3.0 and 3.2.
-
-Unfortunately at the moment these options do not persist in GHC, so you have to give them when compiling application code too.