GitLab

Select verbosity with "make VERBOSE=n". Options so far:
 n=0: No per-test output
 n=1: Only failing test results
 n=2: As above, plus progress information (names of all tests)
 n=3: As aobve, plus commands called.
Default currently is n=3, although n=2 might be a nicer default.

Accidentally broken by my last commit

As a side-effect, the new `{-# MINIMAL #-}` facility (see #7633

) changes
the existing separate warnings for each missing method declaration:

{{{
No explicit method or default declaration for ‛+’
In the instance declaration for ‛Num T’
}}}

to a single warning per class of the following form:

{{{
No explicit implementation for
  ‛+’, ‛*’, ‛abs’, ‛signum’, and ‛fromInteger’
In the instance declaration for ‛Num T’
}}}

This commit adapts the reference output files in the testsuite to follow
this change in GHC's warnings messages.
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

Signed-off-by: Edward Z. Yang <ezyang@mit.edu>

But seems to be fixed in head already.

Expand 'bytes allocated' allowed in haddock.base, and update error
messages.

This closes #3389, and makes the testsuite go through again.

Signed-off-by: Edward Z. Yang <ezyang@mit.edu>

Fixes HostOS bug, where the define was not being set.
Signed-off-by: Edward Z. Yang <ezyang@mit.edu>

Added a new test Makefile variable $(dllext), which is
instantiated to .dll or .so or .dylib depending on your platform.
Signed-off-by: Edward Z. Yang <ezyang@mit.edu>

Signed-off-by: Austin Seipp <austin@well-typed.com>

Signed-off-by: Edward Z. Yang <ezyang@mit.edu>

Signed-off-by: Austin Seipp <austin@well-typed.com>

This includes:

 * Adding a test for bswap16 with a low byte >= 128
 * Also test the byteSwapN functions from GHC.Word, tested both INLINE
   and not INLINE, so we test both independent parts: the compilation of
   base, and the backend compiling the code *using* base.
 * Fix the usage of byteSwapN# primitives in the test, by masking off
 * the higher bits when storing the results in Word16/Word32.

Thanks to Reid Barton for the investigation.
Authored-by: Reid Barton <rwbarton@gmail.com>
Signed-off-by: Austin Seipp <austin@well-typed.com>

Essentially the same tests as for the existing ByteArray# ones.
Signed-off-by: Austin Seipp <austin@well-typed.com>

Signed-off-by: Edward Z. Yang <ezyang@mit.edu>

(this is related to #3647)

Signed-off-by: Edward Z. Yang <ezyang@mit.edu>

Signed-off-by: Edward Z. Yang <ezyang@mit.edu>

Signed-off-by: Edward Z. Yang <ezyang@mit.edu>

Signed-off-by: Edward Z. Yang <ezyang@mit.edu>

Signed-off-by: Edward Z. Yang <ezyang@mit.edu>

Also see http://ghc.haskell.org/trac/ghc/wiki/NewtypeWrappers

This test is a bit speculative, because I can't reproduce problem
on my machine. Still, it should work because it produces the same
Cmm that originally caused the problem.