| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The first change makes the array ones use the proper fixed-size types,
which also means that just like before, they can be used without
explicit conversions with the boxed sized types. (Before, it was Int# /
Word# on both sides, now it is fixed sized on both sides).
For the second change, don't use "extend" or "narrow" in some of the
user-facing primops names for conversions.
- Names like `narrowInt32#` are misleading when `Int` is 32-bits.
- Names like `extendInt64#` are flat-out wrong when `Int is
32-bits.
- `narrow{Int,Word}<N>#` however map a type to itself, and so don't
suffer from this problem. They are left as-is.
These changes are batched together because Alex happend to use the array
ops. We can only use released versions of Alex at this time, sadly, and
I don't want to have to have a release thatwon't work for the final GHC
9.2. So by combining these we get all the changes for Alex done at once.
Bump hackage state in a few places, and also make that workflow slightly
easier for the future.
Bump minimum Alex version
Bump Cabal, array, bytestring, containers, text, and binary submodules
|
|
|
| |
Fixes #17895.
|
|
|
|
| |
Finally fixes #19025.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reduce XZ compression level for regular jobs (it is bumped to 9 for releases
and nightly jobs). In my experiments I've got the following bindist size in
the given time for each compression level (with the quick flavour):
XZ_OPT Time Size
-9 4m06s 112 MB
-8 4m00s 114 MB
-7 3m50s 116 MB
-6 (default) 3m40s 118 MB
-5 2m47s 123 MB
-4 1m57s 134 MB
-3 1m03s 129 MB
-2 49.73s 136 MB
-1 37.72s 142 MB
-0 34.40s 156 MB
|
|
|
|
| |
Due to #19025.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This also means we compile GHC with -O1 instead of -O2 for some
platforms for CI. As a result a lot of test metrics
got worse which we now have to accept.
-------------------------
Metric Increase:
ManyAlternatives
ManyConstructors
MultiLayerModules
Naperian
T10421
T12150
T12227
T12234
T12425
T12545
T12707
T13035
T13253
T13253-spj
T13701
T13379
T13719
T14697
T16577
T18282
T18698a
T18698b
T1969
T3064
T3294
T4801
T5205
T5321FD
T5321Fun
T5631
T6048
T783
T9020
T9203
T9233
T9630
T9872a
T9872b
T9872c
T9872d
T9961
haddock.Cabal
haddock.base
haddock.compiler
parsing001
T5642
WWRec
T14683
T15164
T18304
T18923
-------------------------
|
| |
|
|
|
|
|
| |
It looks like I neglected to update this after introduce flavour
transformers.
|
|
|
|
| |
Also refactor the job definition to eliminate the bug by construction.
|
|
|
|
| |
Ensuring that the right toolchain is used.
|
|
|
|
| |
See #18973.
|
|
|
|
|
| |
The deployments are quite large and yet are currently only served for
the ghc/ghc> project.
|
|
|
|
|
|
|
| |
This adds a job to test cross-compilation from x86-64 to AArch64 with
Hadrian.
Fixes #18234
|
|
|
|
| |
The current Debian 9 image doesn't provide LLVM 7.
|
|
|
|
| |
Namely, those marked with the ~"LLVM backend" label
|
|
|
|
|
|
|
|
| |
This addes the necessary logic to support aarch64 on elf, as well
as aarch64 on mach-o, which Apple calls arm64.
We change architecture name to AArch64, which is the official arm
naming scheme.
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
Haddock chews through enough memory to cause the CI builders to OOM and
there's frankly no reason to build documentation in this job anyways.
|
| | |
|
|/
|
|
| |
Bumps bootstrap compiler to 8.10.1.
|
|
|
|
|
|
|
| |
Previously the Hadrian jobs used the `FLAVOUR` environment variable to
communicate which flavour `ci.sh` should build whereas `make` used
`BUILD_FLAVOUR`. This caused unnecessary confusion. Consolidate these
two.
|
|
|
| |
Silly mistake on my part.
|
|
|
|
| |
Currently the Hadrian build appears not to package documentation correctly,
causing doc-tarball to fail due to the Windows build.
|
| |
|
| |
|
|
|
|
| |
This should have been done when the toolchain was bumped.
|
|
|
|
| |
Fixes #18267.
|
|
|
|
|
|
|
|
| |
As noted in #18726, this regularly breaks. Let's test it.
Note that we don't actually perform a build of GHC itself; we merely
test that the Hadrian executable builds and works (by invoking `hadrian
--version`).
|
| |
|
|
|
|
| |
This should fix #18774.
|
| |
|
| |
|
|
|
|
| |
We now have a proper periodic clean-up script installed on the runners.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
We now generate our Docker images via Dhall definitions, as described in
ghc/ci-images!52. Additionally, we are far more careful about where tools
come from, using the ALEX, HAPPY, HSCOLOR, and GHC environment variables
(set in the Dockerfiles) to find bootstrapping tools.
|
| |
|
|
|
|
| |
A small typo in a rule regular expression.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
This should have been done when we bumped the bootstrap compiler to
8.8.4.
|
|
|
|
|
| |
This interfered with the autoconf variable of the same name, breaking
pre-release builds.
|
| |
|
|
|
|
|
|
|
| |
While these builds are strictly speaking redundant (since every commit
is tested by @marge-bot before making it into `master`), they are nevertheless
useful as they are displayed in the branch's commit list in GitLab's web interface.
Fixes #18595.
|
| |
|
|
|
|
| |
Hopefully this will make the Windows jobs a bit more reliable.
|