1. 16 May, 2003 5 commits
  2. 15 May, 2003 1 commit
  3. 14 May, 2003 5 commits
    • simonmar's avatar
      [project @ 2003-05-14 11:55:11 by simonmar] · 83183fce
      simonmar authored
      Should have been committed with recent SRT changes (see rev. 1.39 of StgSyn.lhs).
      83183fce
    • simonmar's avatar
      [project @ 2003-05-14 09:13:52 by simonmar] · 7a236a56
      simonmar authored
      Change the way SRTs are represented:
      
      Previously, the SRT associated with a function or thunk would be a
      sub-list of the enclosing top-level function's SRT.  But this approach
      can lead to lots of duplication: if a CAF is referenced in several
      different thunks, then it may appear several times in the SRT.
      Let-no-escapes compound the problem, because the occurrence of a
      let-no-escape-bound variable would expand to all the CAFs referred to
      by the let-no-escape.
      
      The new way is to describe the SRT associated with a function or thunk
      as a (pointer+offset,bitmap) pair, where the pointer+offset points
      into some SRT table (the enclosing function's SRT), and the bitmap
      indicates which entries in this table are "live" for this closure.
      The bitmap is stored in the 16 bits previously used for the length
      field, but this rarely overflows.  When it does overflow, we store the
      bitmap externally in a new "SRT descriptor".
      
      Now the enclosing SRT can be a set, hence eliminating the duplicates.
      
      Also, we now have one SRT per top-level function in a recursive group,
      where previously we used to have one SRT for the whole group.  This
      helps keep the size of SRTs down.
      
      Bottom line: very little difference most of the time.  GHC itself got
      slightly smaller.  One bad case of a module in GHC which had a huge
      SRT has gone away.
      
      While I was in the area:
      
        - Several parts of the back-end require bitmaps.  Functions for
          creating bitmaps are now centralised in the Bitmap module.
      
        - We were trying to be independent of word-size in a couple of
          places in the back end, but we've now abandoned that strategy so I
          simplified things a bit.
      7a236a56
    • simonmar's avatar
      [project @ 2003-05-14 09:11:49 by simonmar] · efbac413
      simonmar authored
      Comments only
      efbac413
    • simonmar's avatar
      [project @ 2003-05-14 09:11:06 by simonmar] · c7268677
      simonmar authored
      Calling mmap() with a size > 3Gig results in EINVAL on Linux.  Catch
      this case and report it as an out of memory condition instead of a
      panic.
      c7268677
    • simonmar's avatar
      [project @ 2003-05-14 09:07:28 by simonmar] · 1d0504a9
      simonmar authored
      Comment only
      1d0504a9
  4. 13 May, 2003 2 commits
  5. 12 May, 2003 2 commits
  6. 07 May, 2003 4 commits
  7. 06 May, 2003 7 commits
  8. 04 May, 2003 1 commit
  9. 01 May, 2003 3 commits
  10. 29 Apr, 2003 2 commits
  11. 28 Apr, 2003 3 commits
  12. 27 Apr, 2003 2 commits
  13. 25 Apr, 2003 2 commits
  14. 23 Apr, 2003 1 commit