- Feb 04, 2021
-
-
Ben Gamari authored
Previously we only built Linux bindists with hyperlinked sources.
-
Ben Gamari authored
- Feb 02, 2021
-
-
Ben Gamari authored
Ensure that deb10-dwarf artifacts are preserved. (cherry picked from commit a4f50cd8)
-
- Feb 01, 2021
-
-
Simon Peyton Jones authored
The motivation is given in Note [tcFamTyPats: zonking the result kind]. Fixes #19250 -- the fix is easy. (cherry picked from commit 69cab37a)
-
- Jan 25, 2021
-
-
(cherry picked from commit 4517a382)
-
(cherry picked from commit f065b6b0)
-
Ben Gamari authored
We do not support foreign "C" imports of varargs functions. While this works on amd64, in general the platform's calling convention may need more type information that our Cmm representation can currently provide. For instance, this is the case with Darwin's AArch64 calling convention. Document this fact in the users guide and fix T5423 which makes use of a disallowed foreign import. Closes #18854. (cherry picked from commit 0b772221)
-
Ben Gamari authored
In general we are less careful about locking closures when running with only a single capability. Fixes #19075. (cherry picked from commit 87bc458d)
-
- Jan 06, 2021
-
-
Ben Gamari authored
-
Ben Gamari authored
(cherry picked from commit 61ce4261)
-
Ben Gamari authored
The refactoring in ed57c3a9 failed to initialize this field, resulting in no exports being registered. A very silly bug and yet somehow none of our tests caught it. See #18548. Fixes #19149. (cherry picked from commit 4cd2674f)
-
Ben Gamari authored
Previously lookupSymbol_PEi386 would call lookupSymbol while holding linker_mutex. Fix this by rather calling `lookupDependentSymbol`. This is safe because lookupSymbol_PEi386 unconditionally holds linker_mutex. Happily, this un-breaks `T12771`, `T13082_good`, and `T14611`, which were previously marked as broken due to #18718. Closes #19155. (cherry picked from commit a7105e53)
-
- Jan 02, 2021
-
-
vdukhovni authored
The fix for 18919 was somewhat incomplete: while the MVars were correctly added to the mut_list via dirty_MVAR(), their info table remained "clean". While this is mostly harmless in non-debug builds, but trips an assertion in the debug build, and may result in the MVar being needlessly being added to the mut_list multiple times. Resolves: #19145
-
- Dec 16, 2020
-
-
Ben Gamari authored
Scripts taken from autoconf 90b8cb42ba3b244250a6986b8b78c80f30ed197a
-
Ben Gamari authored
-
Ben Gamari authored
Previously we would append -Werror to the argument list. However, this ended up overriding the -Wno-error=... flags in Settings.Warnings.
-
Ben Gamari authored
The previous state was quite illegible.
-
Ben Gamari authored
-
Ben Gamari authored
This interfered with the autoconf variable of the same name, breaking pre-release builds. (cherry picked from commit 15dca847) (cherry picked from commit 3e55edd9)
-
(cherry picked from commit 57f3fdb1)
- Dec 13, 2020
-
-
Ben Gamari authored
Fixes #18233.
-
This patch adds the upper bound of a happy version for ghc-9.0 and earlier. Currently, we can't use happy-1.20.0 for ghc-9.0. See #18620. (cherry picked from commit 74a7fbff)
-
- Dec 10, 2020
-
-
GHC GitLab CI authored
-
Ben Gamari authored
Previously we would push large objects and compact regions to the mark queue during the deadlock detect GC, resulting in failure to detect deadlocks.
-
GHC GitLab CI authored
Pull the cold non-moving allocation path out of alloc_for_copy.
-
GHC GitLab CI authored
Previously the deadlock-detection promotion logic in alloc_for_copy was just plain wrong: it failed to fire when gct->evac_gen_no != oldest_gen->gen_no. The fix is simple: move the
-
GHC GitLab CI authored
When performing a deadlock-detection GC we must ensure that all objects end up in the non-moving generation. Assert this in scavenge.
-
Ben Gamari authored
Previously an incorrect semicolon meant that we would fail to call busy_wait_nop when spinning.
-
- Dec 07, 2020
-
-
GHC GitLab CI authored
Per request of @phadej.
-
Ben Gamari authored
Pulled out of !4310. (cherry picked from commit be408b86)
-
Ben Gamari authored
As noted in #18991, we would previously allocate heap in low memory. Due to this the linker, which typically *needs* low memory, would end up competing with the heap. In longer builds we end up running out of low memory entirely, leading to linking failures. (cherry picked from commit a1a75aa9)
-
Ben Gamari authored
We place symbol_extras right after bss. We also need to ensure that symbol_extras can be mprotect'd independently from the rest of the image. To ensure this we round up the size of bss to a page boundary, thus ensuring that symbol_extras is also page-aligned. (cherry picked from commit 9f40cf6c) (cherry picked from commit 4b83b6a8)
-
GHC GitLab CI authored
See Note [Non-moving GC: Marking evacuated objects]. (cherry picked from commit b416189e)
-
Ben Gamari authored
(cherry picked from commit a3b8375e)
-
GHC GitLab CI authored
The mark thread is not joinable as we detach from it on creation. (cherry picked from commit ca1ef0e7)
-
GHC GitLab CI authored
pthread_join returns its error code and apparently doesn't set errno. (cherry picked from commit c488ac73)
-
GHC GitLab CI authored
Ensure that the the free variables have been pushed to the update remembered set before we zero the slop. (cherry picked from commit 134f7599)
-
GHC GitLab CI authored
(cherry picked from commit 35c22991)
-