ghc.mk | 8 1 + 7 - 0 !
1 file changed, 1 insertion(+), 7 deletions(-)

---

aclocal.m4 | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 use vfpv3-d16 fpu for arm builds
 Jani writes: The D16 part was Debian/Ubuntu specific, IIRC we define hardfloat

utils/ghc-pkg/Main.hs | 6 4 + 2 - 0 !
1 file changed, 4 insertions(+), 2 deletions(-)

 do not emit a warning if the .haddock file is missing
 As it is quite common on Debian installations to install the -dev package
 without the -doc package.

aclocal.m4 | 5 4 + 1 - 0 !
compiler/utils/Platform.hs | 2 2 + 0 - 0 !
2 files changed, 6 insertions(+), 1 deletion(-)

---

compiler/iface/MkIface.hs | 5 4 + 1 - 0 !
1 file changed, 4 insertions(+), 1 deletion(-)

---

compiler/main/SysTools.hs | 12 10 + 2 - 0 !
1 file changed, 10 insertions(+), 2 deletions(-)

---

driver/ghci/ghc.mk | 4 2 + 2 - 0 !
rules/shell-wrapper.mk | 6 3 + 3 - 0 !
utils/mkdirhier/ghc.mk | 2 1 + 1 - 0 !
3 files changed, 6 insertions(+), 6 deletions(-)

 do not use $shell
 as $SHELL is the user's preferred interactive shell. We do not want this to
 leak into the wrapper scripts.

rts/RtsSymbols.c | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 use native x86_64 instructions on x32
 This patch enables a few native 64-bit integer instructions
 on x32 which are available on this architecture despite using
 32-bit pointers. These instructions are present on x86_64 but
 not on x86 and ghc checks the size of (void *) to determine
 that. This method fails on x32 since despite using 32-bit
 pointers and hence sizeof(void *) == 4, it still uses the
 full x86_64 instruction set and software-emulated variants
 of the aforementioned 64-bit integer instructions are
 therefore not present in the toolchain which will make ghc
 fail to build on x32.
 See: https://ghc.haskell.org/trac/ghc/ticket/11571
 .

ghc.mk | 8 6 + 2 - 0 !
1 file changed, 6 insertions(+), 2 deletions(-)

 use the stage1 binaries for install
 In order to be able to perform a cross-build, we need to use
 the stage1 binaries during installation. Both ghc and ghc-pkg
 are run during the install target and therefore must be able
 to run on the build machine.
 .

utils/ghc-pkg/ghc.mk | 7 6 + 1 - 0 !
utils/hp2ps/ghc.mk | 16 15 + 1 - 0 !
utils/unlit/ghc.mk | 10 9 + 1 - 0 !
3 files changed, 30 insertions(+), 3 deletions(-)

 build unlit and hp2ps twice