Previously the call to dirty_MUT_VAR in stg_atomicModifyMutVarzuzh was
missing its final argument.

Fixes #20414.

These functions really do no marking; they merely trace pointers.

We need to ensure that the TRecChunk itself is marked, in addition to
the TRecs it contains.

Matthew Pickering authored 3 years ago and Marge Bot committed 3 years ago

Given the previous commit, `-V` allows us to see some useful information
in CI (such as the call stack on failure) which normally people don't
want to see.

As a result the $VERBOSE variable now tweaks the diagnostic level one
level higher (to Diagnostic), which produces a lot of output.

Matthew Pickering authored 3 years ago and Marge Bot committed 3 years ago

Before we really only had two verbosity levels, normal and verbose.
There are now three levels:

Normal: Commands show stderr (no stdout) and minimal build failure messages.
Verbose (-V): Commands also show stdout, build failure message contains
              callstack and additional information
Diagnostic (-VV): Very verbose output showing all command lines and passing -v3 to cabal commands.

-V is similar to the default verbosity from before (but a little more
verbose)

Matthew Pickering authored 3 years ago and Marge Bot committed 3 years ago

This change reduces the default verbosity of error messages to omit the
stack trace information from the printed output.

For example, before all errors would have a long call trace:

```
Error when running Shake build system:
  at action, called at src/Rules.hs:39:19 in main:Rules
  at need, called at src/Rules.hs:61:5 in main:Rules
* Depends on: _build/stage1/lib/package.conf.d/ghc-9.3.conf
* Depends on: _build/stage1/compiler/build/libHSghc-9.3.a
* Depends on: _build/stage1/compiler/build/GHC/Tc/Solver/Rewrite.o
* Depends on: _build/stage1/compiler/build/GHC/Tc/Solver/Rewrite.o _build/stage1/compiler/build/GHC/Tc/Solver/Rewrite.hi
  at cmd', called at src/Builder.hs:330:23 in main:Builder
  at cmd, called at src/Builder.hs:432:8 in main:Builder
* Raised the exception:
```

Which can be useful but it confusing for GHC rather than hadrian
developers.

Ticket #20386

Sylvain Henry authored 3 years ago and Marge Bot committed 3 years ago

This flag is used to remove the output of core stats per binding in Core
dumps.

Matthew Pickering authored 3 years ago and Marge Bot committed 3 years ago

Even in -j1 we now fork all the work into it's own thread so that Ctrl-C
exceptions are thrown on the main thread, which is blocked waiting for
the work thread to finish. The default exception handler then picks up
Ctrl-C exception and the dangling thread is killed.

Fixes #20292

Artyom Kuznetsov authored 3 years ago and Marge Bot committed 3 years ago

NoGhcTc is removed from HsMatchContext. As a result of this,
HsMatchContext GhcTc is now a valid type that has Id in it,
instead of Name and tcMatchesFun now takes Id instead of Name.

As of cbfc0e93 we set $HOME to a
non-existent directory to ensure hermeticity.

Ben Gamari authored 3 years ago and Marge Bot committed 3 years ago

Otherwise we are dependent upon the C++ compiler's default language.

Ben Gamari authored 3 years ago and Marge Bot committed 3 years ago

Otherwise we may get warnings from the toolchain if the bootstrap
compiler was built with a different deployment target.

Ben Gamari authored 3 years ago and Marge Bot committed 3 years ago

Previously the C/C++ language version check in STG could throw an
undefined macro warning due to __STDC_VERSION__ when compiled with a C++
compiler. Fix this by defining __STDC_VERSION__==0 when compiling with a
C++ compiler.

Fixes #20394.

Ben Gamari authored 3 years ago and Marge Bot committed 3 years ago

The BSD sed implementation doesn't allow `sed -i COMMAND FILE`; one must
rather use `sed -i -e COMMAND FILE`.

Ben Gamari authored 3 years ago and Marge Bot committed 3 years ago

ipeMap.c failed to #include <string.h>

Ben Gamari authored 3 years ago and Marge Bot committed 3 years ago

Previously the meaning of this flag was unclear and as a result I
suspect that CabalHaveLibffi could be incorrectly False.

Ben Gamari authored 3 years ago and Marge Bot committed 3 years ago

Previously both the --with-system-libffi path and the
non--with-system-libffi path set CabalUseSystemLibFFI=True. This was
wrong.

Ben Gamari authored 3 years ago and Marge Bot committed 3 years ago

Otherwise cabal-install falls over.

Ben Gamari authored 3 years ago and Marge Bot committed 3 years ago

Previously the cache persistence was implemented as various ad-hoc `cp`
commands at the end of the individual CI scripts. Here we move all of
this logic into `ci.sh`.

Ben Gamari authored 3 years ago and Marge Bot committed 3 years ago

`cabal update` is already implied by `ci.sh setup`.

Sven Tennie authored 3 years ago and Marge Bot committed 3 years ago

Emit an Info Table Provenance Entry (IPE) for every stack represeted info table
if -finfo-table-map is turned on.

To decode a cloned stack, lookupIPE() is used. It provides a mapping between
info tables and their source location.

Please see these notes for details:

- [Stacktraces from Info Table Provenance Entries (IPE based stack unwinding)]
- [Mapping Info Tables to Source Positions]

Metric Increase:
    T12545