Skip to content
Snippets Groups Projects
Select Git revision
  • wip/T17747
  • wip/tsan/no-barriers
  • wip/T20076
  • wip/supersven/riscv64-ncg
  • wip/T23109
  • wip/tsan/fixes
  • wip/check-gc
  • master default protected
  • wip/marge_bot_batch_merge_job
  • wip/sand-witch/#23434-wterm-variable-capture
  • wip/expand-do
  • wip/or-pats
  • wip/int-index/hdk-register-tok
  • wip/int-index/tok-where
  • wip/js-number-note-refs
  • wip/t23454
  • wip/T23143
  • wip/sand-witch/#16635-improve-errors
  • wip/T18389-task-zero
  • wip/haddock-mem-fixes
  • ghc-9.2.8-release
  • ghc-9.6.2-release
  • ghc-9.4.5-release
  • ghc-9.6.1-release
  • ghc-9.6.1-rc1
  • ghc-9.2.7-release
  • ghc-9.6.1-alpha3
  • ghc-9.2.6-release
  • ghc-9.6.1-alpha2
  • ghc-9.4.4-release
  • ghc-9.7-start
  • ghc-9.2.5-release
  • ghc-9.4.3-release
  • ghc-9.4.2-release
  • ghc-9.4.1-release
  • ghc-9.2.4-release
  • ghc-9.4.1-rc1
  • ghc-9.4.1-alpha3
  • ghc-9.2.3-release
  • ghc-9.4.1-alpha2
40 results
Compare
Forked from Glasgow Haskell Compiler / GHC
6166 commits behind the upstream repository.
Alan Zimmerman's avatar
EPA: Use Introduce [DeclTag] in AnnSortKey
Alan Zimmerman authored 
The AnnSortKey is used to keep track of the order of declarations for
printing when the container has split them apart.

This applies to HsValBinds and ClassDecl, ClsInstDecl.

When making modifications to the list of declarations, the new order
must be captured for when it must be printed. For each list of
declarations (binds and sigs for a HsValBind) we can just store the
list in order.

To recreate the list when printing, we must merge them, and this is
what the AnnSortKey records. It used to be indexed by SrcSpan, we now
simply index by a marker as to which list to take the next item from.
ab40aa52
History
Alan Zimmerman's avatar ab40aa52
History
Name Last commit Last update
..
config
driver
ghc-config
mk
tests
timeout
.gitignore
LICENSE
LICENSE.GPL
Makefile
README.md
README.md

GHC Testsuite Readme

For the full testsuite documentation, please see here.

Quick Guide

Commands to run testsuite:

  • Full testsuite: hadrian/build test
  • Using more threads: hadrian/build test -j12
  • Reduced (fast) testsuite: hadrian/build test --test-speed=fast
  • Run a specific test: hadrian/build test --only="tc055 tc054"
  • Test a specific 'way': hadrian/build test --test-way=optllvm
  • Skip performance tests: hadrian/build test --skip-perf
  • Set verbosity: hadrian/build test --test-verbose=<n> where n=0: No per-test output, n=1: Only failures, n=2: Progress output, n=3: Include commands called (default), n=4: Include perf test results unconditionally, n=5: Echo commands in subsidiary make invocations

Testsuite Ways

The testsuite can be run in a variety of 'ways'. This concept refers to different ways that GHC can compile the code. For example, using the native code generator (-fasm) is one way, while using the LLVM code generator (-fllvm) is another way.

The various ways that GHC supports are defined in config/ghc

Adding Tests

Please see the more extensive documentation here.