1. 19 Dec, 2011 2 commits
    • dmp's avatar
      Hide STG register declarations for LLVM C compilers · f542da48
      dmp authored
      This commit swaps the import order of Rts.h and Stg.h in
      StgCRun.c for non-SPARC architectures. Swapping the import
      order prevents the declaration of the global registers thus
      allowing the GHC runtime to be compiled by LLVM-based C
      LLVM-base C compilers cannot use the global register
      declarations (for R1, R2, etc.) because they use
      GCC-specific extensions. The declarations are not needed in
      StgCRun.c except for the SPARC architecture. The other
      architectures use hand-written assembly that accesses the
      appropriate register directly.
    • Simon Marlow's avatar
  2. 18 Dec, 2011 2 commits
  3. 16 Dec, 2011 2 commits
  4. 15 Dec, 2011 5 commits
    • Ian Lynagh's avatar
      Remove some dead code · 40ef62f6
      Ian Lynagh authored
    • dimitris's avatar
    • Simon Marlow's avatar
      Fix a path, and strip out C++ comments too · 3d7e772f
      Simon Marlow authored
    • Simon Marlow's avatar
      Support for reducing the number of Capabilities with setNumCapabilities · 9bae7915
      Simon Marlow authored
      This patch allows setNumCapabilities to /reduce/ the number of active
      capabilities as well as increase it.  This is particularly tricky to
      do, because a Capability is a large data structure and ties into the
      rest of the system in many ways.  Trying to clean it all up would be
      extremely error prone.
      So instead, the solution is to mark the extra capabilities as
      "disabled".  This has the following consequences:
        - threads on a disabled capability are migrated away by the
          scheduler loop
        - disabled capabilities do not participate in GC
          (see scheduleDoGC())
        - No spark threads are created on this capability
          (see scheduleActivateSpark())
        - We do not attempt to migrate threads *to* a disabled
          capability (see schedulePushWork()).
      So a disabled capability should do no work, and does not participate
      in GC, although it remains alive in other respects.  For example, a
      blocked thread might wake up on a disabled capability, and it will get
      quickly migrated to a live capability.  A disabled capability can
      still initiate GC if necessary.  Indeed, it turns out to be hard to
      migrate bound threads, so we wait until the next GC to do this (see
      comments for details).
    • dimitris's avatar
  5. 14 Dec, 2011 5 commits
  6. 13 Dec, 2011 20 commits
  7. 12 Dec, 2011 4 commits