1. 12 Apr, 2012 4 commits
  2. 11 Apr, 2012 10 commits
  3. 10 Apr, 2012 4 commits
  4. 09 Apr, 2012 1 commit
  5. 06 Apr, 2012 1 commit
  6. 05 Apr, 2012 10 commits
  7. 04 Apr, 2012 10 commits
    • dterei's avatar
      --amend · 7f61ae25
      dterei authored
      7f61ae25
    • dterei's avatar
      Fix GHC API with respect to safe haskell. (#5989) · 5a0b8270
      dterei authored
      This fixes haddock so it correctly reports
      the safe haskell mode of a module.
      5a0b8270
    • dterei's avatar
      Update safe haskell error/warn formatting · 7ed67597
      dterei authored
      7ed67597
    • dterei's avatar
      c690214d
    • dterei's avatar
      Fix uneeded test in safe haskell code · 2bf60839
      dterei authored
      2bf60839
    • Mikolaj Konarski's avatar
      Add the GC_GLOBAL_SYNC event marking that all caps are stopped for GC · c294d95d
      Mikolaj Konarski authored
      Quoting design rationale by dcoutts: The event indicates that we're doing
      a stop-the-world GC and all other HECs should be between their GC_START
      and GC_END events at that moment. We don't want to use GC_STATS_GHC
      for that, because GC_STATS_GHC is for extra GHC-specific info,
      not something we have to rely on to be able to match the GC pauses
      across HECs to a particular global GC.
      c294d95d
    • Mikolaj Konarski's avatar
      Fix the timestamps in GC_START and GC_END events on the GC-initiating cap · 598109eb
      Mikolaj Konarski authored
      There was a discrepancy between GC times reported in +RTS -s
      and the timestamps of GC_START and GC_END events on the cap,
      on which +RTS -s stats for the given GC are based.
      This is fixed by posting the events with exactly the same timestamp
      as generated for the stat calculation. The calls posting the events
      are moved too, so that the events are emitted close to the time instant
      they claim to be emitted at. The GC_STATS_GHC was moved, too, ensuring
      it's emitted before the moved GC_END on all caps, which simplifies tools code.
      598109eb
    • Duncan Coutts's avatar
      Emit final heap alloc events and rearrange code to calculate alloc totals · 1f809ce6
      Duncan Coutts authored
      In stat_exit we want to emit a final EVENT_HEAP_ALLOCATED for each cap
      so that we get the same total allocation count as reported via +RTS -s.
      To do so we need to update the per-cap total_allocated counts.
      
      Previously we had a single calcAllocated(rtsBool) function that counted
      the large allocations and optionally the nurseries for all caps. The GC
      would always call it with false, and the stat_exit always with true.
      The reason for these two modes is that the GC counts the nurseries via
      clearNurseries() (which also updates the per-cap total_allocated
      counts), so it's only the stat_exit() path that needs to count them.
      
      We now split the calcAllocated() function into two: countLargeAllocated
      and updateNurseriesStats. As the name suggests, the latter now updates
      the per-cap total_allocated counts, in additon to returning a total.
      1f809ce6
    • Duncan Coutts's avatar
      Move trace of cap delete from shutdownCapability to freeCapability · e88f1625
      Duncan Coutts authored
      Will let us do final per-cap trace events from stat_exit().
      Otherwise we would end up with eventlogs with events for caps
      that have already been deleted.
      e88f1625
    • Duncan Coutts's avatar
      Adjust the eventlog description header for the spark counter event · a3cdefd2
      Duncan Coutts authored
      The EventLogFormat.h described the spark counter fields in a different
      order to that which ghc emits (the GC'd and fizzled fields were
      reversed). At this stage it is easier to fix the ghc-events lib and
      to have ghc continue to emit them in the current order.
      a3cdefd2