1. 24 Aug, 2010 3 commits
  2. 23 Aug, 2010 3 commits
  3. 18 Jul, 2010 1 commit
    • marcotmarcot's avatar
      Don't check for swept blocks in -DS. · eff182c3
      marcotmarcot authored
      The checkHeap function assumed the allocated part of the block contained only
      alive objects and slops.  This was not true for blocks that are collected using
      mark sweep.  The code in this patch skip the test for this kind of blocks.
  4. 22 Aug, 2010 7 commits
  5. 20 Aug, 2010 1 commit
  6. 19 Aug, 2010 6 commits
  7. 17 Aug, 2010 1 commit
  8. 18 Aug, 2010 4 commits
  9. 17 Aug, 2010 1 commit
  10. 16 Aug, 2010 2 commits
  11. 15 Aug, 2010 3 commits
  12. 13 Aug, 2010 1 commit
  13. 12 Aug, 2010 1 commit
  14. 13 Aug, 2010 6 commits
    • dterei's avatar
      LLVM: Enable shared lib support on Linux x64 · 60873542
      dterei authored
    • simonpj@microsoft.com's avatar
      Re-do the arity calculation mechanism again (fix Trac #3959) · 63595209
      simonpj@microsoft.com authored
      After rumination, yet again, on the subject of arity calculation,
      I have redone what an ArityType is (it's purely internal to the
      CoreArity module), and documented it better.  The result should
      fix #3959, and I hope the related #3961, #3983.
      There is lots of new documentation: in particular
       * Note [ArityType]  
         describes the new datatype for arity info
       * Note [State hack and bottoming functions] 
         says how bottoming functions are dealt with, particularly
         covering catch# and Trac #3959
      I also found I had to be careful not to eta-expand single-method
      class constructors; see Note [Newtype classes and eta expansion].
      I think this part could be done better, but it works ok.
    • simonpj@microsoft.com's avatar
      Comments only · 02ec3766
      simonpj@microsoft.com authored
    • simonpj@microsoft.com's avatar
      Modify FloatOut to fix Trac #4237 · d49e8592
      simonpj@microsoft.com authored
      The problem was that a strict binding was getting floated
      out into a letrec. This only happened when profiling was
      on.  It exposed a fragility in the floating strategy.  This
      patch makes it more robust.  See
            Note [Avoiding unnecessary floating]
    • simonpj@microsoft.com's avatar
      Fix egregious bug in SetLevels.notWorthFloating · ff094439
      simonpj@microsoft.com authored
      This bug just led to stupid code, which would
      later be optimised away, but better not to generate
      stupid code in the first place.
    • simonpj@microsoft.com's avatar
      Delete GhcLibProfiled · 1caf694c
      simonpj@microsoft.com authored
      Simon M and I looked at this, and we think GhcLibProfiled is
      (a) not needed (b) confusing.
      Ian should review.
      Really, if GhcProfiled is on we should also 
      check that 'p' is in the GhcLibWays