## Package: ghc / 8.8.1+dfsg1+is+8.6.5+dfsg1-2

Package Version Patches format
ghc 8.8.1+dfsg1+is+8.6.5+dfsg1-2 3.0 (quilt)

### Patch series

view the series file
Patch File delta Description

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.


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

---

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.
.



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.
.


llvm-targets | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 with new ghc 8.4.3, the armel situation seems to have improved,
apply this patch unconditionally.


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

 driver: skip -bsymbolic on unregisterised targets
Trac #15338 is yet another example where -Bsymbolic breaks
semantics of a C program: global variable duplication happens
and unsafePerformIO creates two stdout copies.
.
When -Bsymbolic is not used both C compiler and linker agree
on how global variables are handled. In case of sh4 it consists
on a few assertions:
.
1. global variable is exported from shared library
2. code is referred to this variable via GOT-like mechanism to allow
interposition
3. global variable is present .bss section on an executable
(as an R_*_COPY relocation: symbol contents is copied at executable
startup time)
4. and symbol in executable interposes symbol in shared library.
.
This way both code in shared library and code in executable refer
to a copy of global variable in .bss section of an executable.
.
Unfortunately -Bsymbolic option breaks assumption [2.] and generates
direct references to the symbol. This causes mismatch between
values seen from executable and values seen from shared library code.
.
This change disables '-Bsymbolic' for unregisterised targets.



rts/posix/OSMem.c | 4 4 + 0 - 0 !
1 file changed, 4 insertions(+)

 fix osreserveheapmemory block alignment


libraries/ghc-prim/aclocal.m4 | 2 1 + 1 - 0 !
libraries/ghc-prim/configure.ac | 2 1 + 1 - 0 !
2 files changed, 2 insertions(+), 2 deletions(-)

---

aclocal.m4 | 5 4 + 1 - 0 !
1 file changed, 4 insertions(+), 1 deletion(-)

 add kfreebsdgnu to ghc_convert_os in aclocal.m4


docs/users_guide/conf.py | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

---

includes/rts/storage/ClosureTypes.h | 6 6 + 0 - 0 !
includes/stg/MiscClosures.h | 10 10 + 0 - 0 !
2 files changed, 16 insertions(+)

 allow unregisterised ghc-8.4 to build newer ghc
Commit 4075656e8bb introduced a regression stopping existing unregisteristed
compilers from being able to compile newer versions of GHC. The problem is
that the bootstrap compiler uses the newer rts/storage/ClosureTypes.h file
where some defines have been renamed, resulting in the following error:
.
error: ‘stg_MUT_ARR_PTRS_FROZEN0_info’ undeclared (first use in this function); did you mean ‘stg_MUT_ARR_PTRS_FROZEN_DIRTY_info’?
.
.
This patch can be removed, once ghc-8.4 is no longer the bootstrap compiler.


aclocal.m4 | 8 7 + 1 - 0 !
1 file changed, 7 insertions(+), 1 deletion(-)

 cherry-pick of upstream commits
beba89a0f16681c85d39fc8a894bde4162ff492a.patch:
5e63a25249f3cb07300258e115af9ff55079d2ea.patch:


compiler/cmm/PprC.hs | 24 23 + 1 - 0 !
1 file changed, 23 insertions(+), 1 deletion(-)

---

compiler/nativeGen/PPC/CodeGen.hs | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 powerpc32: fix 64-bit comparison
On powerpc32 64-bit comparison code generated dangling
target labels. This caused ghc build failure as:

\$ ./configure --target=powerpc-unknown-linux-gnu && make
...
SCCs aren't in reverse dependent order
label name but did not place the label into cmp_lo code block.
The change adds the cmp_lo label into the case of negative