Forked from Glasgow Haskell Compiler / GHC

10780 commits behind the upstream repository.

Fixes to dealing with the export of main

Simon Peyton Jones authored 4 years ago

It's surprisingly tricky to deal with 'main' (#19397). This
patch does quite bit of refactoring do to it right. Well,
more-right anyway!

The moving parts are documented in GHC.Tc.Module
   Note [Dealing with main]

Some other oddments:

* Rename tcRnExports to rnExports; no typechecking here!

* rnExports now uses checkNoErrs rather than failIfErrsM;
  the former fails only if rnExports itself finds errors

* Small improvements to tcTyThingCategory, which ultimately
  weren't important to the patch, but I've retained as
  a minor improvement.

8fe274e2

History

8fe274e2 4 years ago

History

Name	Last commit	Last update
..
config
driver
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: make
Using more threads: make THREADS=12
Reduced (fast) testsuite: make fast
Run a specific test: make TEST=tc054
Test a specific 'way': make WAY=optllvm
Keeping the run directory after test run: make CLEANUP=0. You will find a directory {test_name}.run in the test's source directory.
Test a specific stage of GHC: make stage=1
Skip performance tests: make SKIP_PERF_TESTS=YES
Set verbosity: make 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
Pass in extra GHC options: make EXTRA_HC_OPTS=-fvectorize

You can also change directory to a specific test folder to run that individual test or group of tests. For example:

$ cd tests/array
$ make

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.