Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • wip/romes/12935
  • wip/strings
  • wip/T23479
  • wip/marge_bot_batch_merge_job
  • wip/supersven/ghc-toolchain-fuse-ld-bfd-flag
  • wip/haskell-nix-patches/musl64/ghc-9.6-missing-symbols-deadbeef
  • wip/rm-ghc-internal-pack
  • wip/ncg-simd
  • wip/T25257
  • wip/T25243
  • wip/jade/ast
  • wip/ttg-booleanformula
  • wip/supersven/riscv64-cross-ci
  • wip/supersven/aarch64-jump-tables
  • wip/T23847
  • wip/aidylns/ttg-remove-hsunboundvar-via-hshole
  • wip/T25196
  • wip/array-0.5.8.0
  • wip/az/epa-exactprint-sync
  • ghc-9.6.6-release
  • ghc-9.10.1-release
  • ghc-9.10.1-rc1
  • ghc-9.6.5-release
  • ghc-9.10.1-alpha3
  • ghc-9.10.1-alpha2
  • ghc-9.10.1-alpha1
  • ghc-9.11-start
  • ghc-9.8.2-release
  • ghc-9.6.4-release
  • ghc-9.4.8-release
  • ghc-9.8.1-release
  • ghc-9.8.1-rc1
  • ghc-9.6.3-release
  • ghc-9.8.1-alpha4
  • ghc-9.4.7-release
  • ghc-9.8.1-alpha3
  • ghc-9.8.1-alpha2
  • ghc-9.4.6-release
  • ghc-9.8.1-alpha1
40 results
Forked from Glasgow Haskell Compiler / GHC
93 commits behind the upstream repository.
Teo Camarasu's avatar
Implement user-defined allocation limit handlers
Teo Camarasu authored 
Allocation Limits allow killing a thread if they allocate more than a
user-specified limit.
We extend this feature to allow more versatile behaviour.

- We allow not killing the thread if the limit is exceeded.
- We allow setting a custom handler to be called when the limit is exceeded.

User-specified allocation limit handlers run in a fresh thread and are passed
the ThreadId of the thread that exceeded its limit.

We introduce utility functions for getting and setting the allocation
limits of other threads, so that users can reset the limit of a thread
from a handler. Both of these are somewhat coarse-grained as we are
unaware of the allocations in the current nursery chunk.

We provide several examples of usages in testsuite/tests/rts/T22859.hs

Resolves #22859
ea2c6673
History
Teo Camarasu's avatar ea2c6673
History
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
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.