summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Remove GENERATED pragma, as it is not being usedwip/T18639-remove-generated-pragmaAlan Zimmerman2020-09-0818-67/+2
| | | | | | | | | | | | | | | | | | | | | @alanz pointed out on ghc-devs that the payload of this pragma does not appear to be used anywhere. I (@bgamari) did some digging and traced the pragma's addition back to d386e0d2 (way back in 2006!). It appears that it was intended to be used by code generators for use in informing the code coveraging checker about generated code provenance. When it was added it used the pragma's "payload" fields as source location information to build an "ExternalBox". However, it looks like this was dropped a year later in 55a5d8d9. At this point it seems like the pragma serves no useful purpose. Given that it also is not documented, I think we should remove it. Updates haddock submodule Closes #18639
* gitlab-ci: Use hadrian builds for Windows release artifactsBen Gamari2020-09-071-7/+11
|
* gitlab-ci: Configure bignum backend in Hadrian buildsBen Gamari2020-09-071-0/+2
|
* Add clarification regarding poll/kqueue flagsWander Hillen2020-09-071-2/+6
|
* gitlab-ci: Fix typoBen Gamari2020-09-051-1/+1
| | | | A small typo in a rule regular expression.
* testsuite: Mark T5975[ab] as broken on WindowsBen Gamari2020-09-051-2/+5
| | | | Due to #7305.
* testsuite: Drop Windows-specific output for parseTreeBen Gamari2020-09-051-160/+0
| | | | The normalise_slashes normaliser should handle this.
* gitlab-ci: Drop Windows make jobBen Gamari2020-09-051-6/+3
| | | | | | These are a significant burden on our CI resources and end up failing quite often due to #18274. Here I drop the make jobs during validaion; it is now run only during the nightly builds.
* gitlab-ci: Bump Windows toolchain versionBen Gamari2020-09-051-1/+1
| | | | | This should have been done when we bumped the bootstrap compiler to 8.8.4.
* gitlab-ci: Rename RELEASE variable to RELEASE_JOBBen Gamari2020-09-051-1/+1
| | | | | This interfered with the autoconf variable of the same name, breaking pre-release builds.
* gitlab-ci: More intelligent detection of locale availabilityBen Gamari2020-09-051-3/+26
| | | | | | | | Previously ci.sh would unconditionally use C.UTF-8. However, this fails on Centos 7, which appears not to provide this locale. Now we first try C.UTF-8, then try en_US.UTF-8, then fail. Works around #18607.
* configure: Fix whitespaceBen Gamari2020-09-051-68/+68
|
* rts: Consistently use stgMallocBytes instead of mallocGHC GitLab CI2020-09-055-37/+32
| | | | | This can help in debugging RTS memory leaks since all allocations go through the same interface.
* Move Hadrian's wiki pages in tree (fix #16165)Sylvain Henry2020-09-041-0/+104
| | | | | Only the debugging page contains interesting stuff. Some of this stuff looks old (e.g. recommending "cabal install")...
* Documented the as of yet undocumented '--print-*' GHC flags,Benjamin Maurer2020-09-044-21/+209
| | | | | | as well as `-split-objs`, since that is related to `--print-object-splitting-supported`. See #18641
* configure: Avoid hard-coded ld path on WindowsGHC GitLab CI2020-09-047-24/+45
| | | | | | | The fix to #17962 ended up regressing on Windows as it failed to replicate the logic responsible for overriding the toolchain paths on Windows. This resulted in a hard-coded path to a directory that likely doesn't exist on the user's system (#18550).
* Introduce isBoxedTupleDataCon and use it to fix #18644Ryan Scott2020-09-0418-28/+40
| | | | | | | | | | | | | | | | | | | | The code that converts promoted tuple data constructors to `IfaceType`s in `GHC.CoreToIface` was using `isTupleDataCon`, which conflates boxed and unboxed tuple data constructors. To avoid this, this patch introduces `isBoxedTupleDataCon`, which is like `isTupleDataCon` but only works for _boxed_ tuple data constructors. While I was in town, I was horribly confused by the fact that there were separate functions named `isUnboxedTupleCon` and `isUnboxedTupleTyCon` (similarly, `isUnboxedSumCon` and `isUnboxedSumTyCon`). It turns out that the former only works for data constructors, despite its very general name! I opted to rename `isUnboxedTupleCon` to `isUnboxedTupleDataCon` (similarly, I renamed `isUnboxedSumCon` to `isUnboxedSumDataCon`) to avoid this potential confusion, as well as to be more consistent with the naming convention I used for `isBoxedTupleDataCon`. Fixes #18644.
* DynFlags: don't pass DynFlags to cmmImplementSwitchPlansSylvain Henry2020-09-042-6/+6
|
* DynFlags: use Platform in foldRegs*Sylvain Henry2020-09-049-152/+138
|
* Don't rely on CLabel's Outputable instance in CmmToCSylvain Henry2020-09-042-20/+21
| | | | | This is in preparation of the removal of sdocWithDynFlags (#10143), hence of the refactoring of CLabel's Outputable instance.
* expected-undocumented-flags remove kill flagsKathryn Spiers2020-09-031-2/+0
| | | | It looks like the flags were removed in https://gitlab.haskell.org/ghc/ghc/-/commit/3e27205a66b06a4501d87eb31e285eadbc693eb7 and can safely be removed here
* configure: Work around Raspbian's silly packaging decisionsBen Gamari2020-09-031-19/+34
| | | | See #17856.
* Bignum: add missing compat import/export functionsSylvain Henry2020-09-021-3/+30
|
* Remove outdated noteSylvain Henry2020-09-021-29/+0
|
* Remove potential space leak from Data.List.transposeDavid Feuer2020-09-021-1/+7
| | | | | | | | | Previously, `transpose` produced a list of heads and a list of tails independently. This meant that a function using only some heads, and only some tails, could potentially leak space. Use `unzip` to work around the problem by producing pairs and selector thunks instead. Time and allocation behavior will be worse, but there should be no more leak potential.
* Turn on -XMonoLocalBinds by default (#18430)Sebastian Graf2020-09-027-11/+17
| | | | | | | | | And fix the resulting type errors. Co-authored-by: Krzysztof Gogolewski <krz.gogolewski@gmail.com> Metric Decrease: parsing001
* testsuite: Add broken test for #18302Ben Gamari2020-09-013-0/+13
|
* Remove "Ord FastString" instanceSylvain Henry2020-09-0132-113/+237
| | | | | | | | | | | | | | | | | | | FastStrings can be compared in 2 ways: by Unique or lexically. We don't want to bless one particular way with an "Ord" instance because it leads to bugs (#18562) or to suboptimal code (e.g. using lexical comparison while a Unique comparison would suffice). UTF-8 encoding has the advantage that sorting strings by their encoded bytes also sorts them by their Unicode code points, without having to decode the actual code points. BUT GHC uses Modified UTF-8 which diverges from UTF-8 by encoding \0 as 0xC080 instead of 0x00 (to avoid null bytes in the middle of a String so that the string can still be null-terminated). This patch adds a new `utf8CompareShortByteString` function that performs sorting by bytes but that also takes Modified UTF-8 into account. It is much more performant than decoding the strings into [Char] to perform comparisons (which we did in the previous patch). Bump haddock submodule
* Fix FastString lexicographic ordering (fix #18562)Sylvain Henry2020-09-014-1/+11
|
* Bignum: add BigNat compat functions (#18613)Sylvain Henry2020-08-311-0/+54
|
* Limit upper version of Happy for ghc-9.2 (#18620)Takenobu Tani2020-08-312-3/+3
| | | | | | | | This patch adds the upper bound of a happy version for ghc-9.2. Currently, We can use happy-1.19 or happy-1.20 for ghc-9.2. See #18620.
* Limit upper version of Happy for ghc-9.0 and earlier (#18620)Takenobu Tani2020-08-312-1/+3
| | | | | | | | | 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.
* Ignore more filesSven Tennie2020-08-311-2/+9
| | | | | Ignore files from "new style" cabal builds (dist-newstyle folders) and from clangd (C language server).
* Set the dynamic-system-linker flag to ManualMoritz Angermann2020-08-311-1/+1
| | | | This flag should be user controllable, hence Manual: True.
* Fix documentation and fix "check" bignum backend (#18604)Sylvain Henry2020-08-315-19/+19
|
* Don't store HomeUnit in UnitConfigSylvain Henry2020-08-311-17/+22
| | | | | Allow the creation of a UnitConfig (hence of a UnitState) without having a HomeUnit. It's required for #14335.
* [fixup 3433] move debugBelch into IF_DEBUG(linker)Moritz Angermann2020-08-311-2/+3
| | | | | | | | The commit in dff1cb3d9c111808fec60190747272b973547c52 incorrectly left the `debugBelch` function without a comment or IF_DEBUG(linker,) decoration. This rectifies it. Needs at least a 8.10 backport, as it was backported in 6471cc6aff80d5deebbdb1bf7b677b31ed2af3d5
* Dominators.hs: Use unix line endingsAndreas Klebinger2020-08-311-563/+563
|
* Update dominator code with fixes from the dom-lt package.Andreas Klebinger2020-08-311-83/+49
| | | | | Two bugs turned out in the package that have been fixed since. This MR includes this fixes in the GHC port of the code.
* Hadrian: fix slow-validate flavour (#18586)Sylvain Henry2020-08-311-1/+6
|
* Bump Win32 and process submodulesBen Gamari2020-08-312-0/+0
|
* Add additional tests for #18172 (Followup MR 3543)Roland Senn2020-08-313-0/+22
| | | | | | | There was still one active discussion [thread](https://gitlab.haskell.org/ghc/ghc/-/merge_requests/3543#note_284325) when MR !3543 got merged. This MR adds the requested tests exercising the changes in `compiler/GHC/HsToCore/Match/Literal.hs:warnAboutEmptyEnumerations` and its sub-functions.
* Add tests for #15617.Roland Senn2020-08-313-0/+9
| | | | Avoid a similar regression in the future.
* base: Better error message on invalid getSystemTimerManager callBen Gamari2020-08-311-2/+4
| | | | | | | | | Previously we would produce a rather unhelpful pattern match failure error in the case where the user called `getSystemTimerManager` in a program which isn't built with `-threaded`. This understandably confused the user in #15616. Fixes #15616.
* document how build system find toolchains on WindowsTamar Christina2020-08-288-12/+83
|
* Fix use distro toolchianTamar Christina2020-08-288-4/+19
|
* Add missing primop documentation (#18454)Krzysztof Gogolewski2020-08-288-56/+137
| | | | | | | | | | | | | | | - Add three pseudoops to primops.txt.pp, so that Haddock renders the documentation - Update comments - Remove special case for "->" - it's no longer exported from GHC.Prim - Remove reference to Note [Compiling GHC.Prim] - the ad-hoc fix is no longer there after updates to levity polymorphism. - Document GHC.Prim - Remove the comment that lazy is levity-polymorphic. As far as I can tell, it never was: in 80e399639, only the unfolding was given an open type variable. - Remove haddock hack in GHC.Magic - no longer neccessary after adding realWorld# to primops.txt.pp.
* Make {hsExpr,hsType,pat}NeedsParens aware of boxed 1-tuplesRyan Scott2020-08-276-1/+53
| | | | | | | | | | | | `hsExprNeedsParens`, `hsTypeNeedsParens`, and `patNeedsParens` previously assumed that all uses of explicit tuples in the source syntax never need to be parenthesized. This is true save for one exception: boxed one-tuples, which use the `Solo` data type from `GHC.Tuple` instead of special tuple syntax. This patch adds the necessary logic to the three `*NeedsParens` functions to handle `Solo` correctly. Fixes #18612.
* Consolidate imports in getMinimalImports (#18264)Aditya Gupta2020-08-275-3/+54
|
* primops: Remove Monadic and Dyadic categoriesKrzysztof Gogolewski2020-08-268-207/+152
| | | | | | | | | There were four categories of primops: Monadic, Dyadic, Compare, GenPrimOp. The compiler does not treat Monadic and Dyadic in any special way, we can just replace them with GenPrimOp. Compare is still used in isComparisonPrimOp.
View Lorry Controller Status