This project is mirrored from https://gitlab.haskell.org/ghc/ghc.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
  1. 09 Dec, 2013 1 commit
  2. 04 Dec, 2013 2 commits
  3. 24 Nov, 2013 1 commit
  4. 15 Nov, 2013 1 commit
    • Duncan Coutts's avatar
      Fix up test topHandler03 by ignoring unhelpful shell output · 14527c19
      Duncan Coutts authored
      Shells! Grrrr. Some shells print out a message if your program terminates with
      a signal. In the case of topHandler03 which deliberately exits with signal 15
      SIGTERM, some shells were printing "Terminated" to stdout.
      
      Why the testsuite driver goes via a shell I do not know (it also messes up the
      exit codes for signals).
      14527c19
  5. 14 Nov, 2013 2 commits
    • Duncan Coutts's avatar
      Add tests for the top level exception handler · 2ec9734d
      Duncan Coutts authored
      The top level exception handler is wrapped around main, and FFI exports.
      It handles exceptions that are not otherwise caught in user code. For
      most exception is just prints them, but handles a few specially,
      including ExitCode and UserInterrupt.
      
      On Unix it installs a signal handler for SIGINT to translate it into a
      UserInterrupt async exception.
      
      So we test that:
      
      1. receiving SIGINT does trigger a UserInterrupt async exception
      2. an unhandled UserInterrupt makes us kill ourselves with SIGINT
      3. an unhandled ExitFailure (-sig) makes us kill ourselves with sig
      2ec9734d
    • Duncan Coutts's avatar
      Handle ExitFailure (-sig) by killing process with signal · 643f07c6
      Duncan Coutts authored
      On Unix we now use negative exit codes in ExitFailure to indicate that a
      process exited due to a signal. This patch implements the case for when
      a ExitFailure exception propagates out of the top of main (and is
      handled by the topHandler).
      
      For a negative ExitFailure code, we try to kill the process using that
      signal (the details of that are handled by shutdownHaskellAndSignal from
      the RTS). For an exit code outside the valid ranges, we use 0xff.
      643f07c6
  6. 08 Nov, 2013 1 commit
  7. 07 Nov, 2013 2 commits
    • Merijn Verstraaten's avatar
      *Really* RTS crash due to bad coercion. · 33ed16bd
      Merijn Verstraaten authored
      
      
      Previous commit only moved the coercion mistake to a different
      architecture (i.e. underflow could still occur on platforms where Int
      is smaller than CInt). This patch should definitively deal with all
      possible combinations.
      Signed-off-by: thoughtpolice's avatarAustin Seipp <aseipp@pobox.com>
      33ed16bd
    • Merijn Verstraaten's avatar
      Fix OSX RTS crash due to bad coercion. · 00e04e81
      Merijn Verstraaten authored
      
      
      The code coerces Int to CInt, which causes an overflow if Int is bigger
      than CInt (for example, Int 64bit, CInt 32 bit). This results in a
      negative value being passed to c_poll.
      
      On Linux all negative values are treated as infinite timeouts, which
      gives subtly wrong semantics, but is unlikely to produce actual bugs.
      
      OSX insists that only -1 is a valid value for infinite timeout, any
      other negative timeout is treated as an invalid argument.
      
      This patch replaces the c_poll call with a loop that handles the
      overflow gracefully by chaining multiple calls to poll to obtain the
      proper semantics.
      Signed-off-by: thoughtpolice's avatarAustin Seipp <aseipp@pobox.com>
      00e04e81
  8. 01 Nov, 2013 3 commits
  9. 31 Oct, 2013 1 commit
    • eir@cis.upenn.edu's avatar
      Add new module Data.Type.Bool, defining &&, || and Not. · 9265c889
      eir@cis.upenn.edu authored
      This change was necessary given the instances for (==) in
      Data.Type.Equality. These need conjunction, and a local
      definition of conjunction doesn't work if a client is reasoning
      about equality. Both the client and the library need the
      same conjunction, so that is what Data.Type.Bool provides.
      9265c889
  10. 28 Oct, 2013 4 commits
  11. 27 Oct, 2013 2 commits
  12. 25 Oct, 2013 2 commits
  13. 24 Oct, 2013 1 commit
  14. 18 Oct, 2013 1 commit
  15. 16 Oct, 2013 1 commit
  16. 14 Oct, 2013 1 commit
  17. 12 Oct, 2013 2 commits
  18. 10 Oct, 2013 1 commit
  19. 09 Oct, 2013 1 commit
  20. 07 Oct, 2013 1 commit
  21. 05 Oct, 2013 2 commits
  22. 03 Oct, 2013 3 commits
  23. 02 Oct, 2013 1 commit
    • Austin Seipp's avatar
      Fix Windows build. · 47dd3c22
      Austin Seipp authored
      
      
      In dfb52c3d the default language was set to Haskell2010 - by default,
      GHC is less strict about the layout rule (controlled by
      -XNonincreasingIndentation), but not when we explicitly set the language
      to H2010. It turns out we relied on this behavior in the Windows build.
      
      Thanks to Reid Barton for pointing this out.
      Signed-off-by: default avatarAustin Seipp <austin@well-typed.com>
      47dd3c22
  24. 30 Sep, 2013 2 commits
  25. 29 Sep, 2013 1 commit