1. 29 Jul, 2007 1 commit
  2. 27 Jul, 2007 1 commit
    • Simon Marlow's avatar
      Pointer Tagging · 6015a94f
      Simon Marlow authored
        
      This patch implements pointer tagging as per our ICFP'07 paper "Faster
      laziness using dynamic pointer tagging".  It improves performance by
      10-15% for most workloads, including GHC itself.
      
      The original patches were by Alexey Rodriguez Yakushev
      <mrchebas@gmail.com>, with additions and improvements by me.  I've
      re-recorded the development as a single patch.
      
      The basic idea is this: we use the low 2 bits of a pointer to a heap
      object (3 bits on a 64-bit architecture) to encode some information
      about the object pointed to.  For a constructor, we encode the "tag"
      of the constructor (e.g. True vs. False), for a function closure its
      arity.  This enables some decisions to be made without dereferencing
      the pointer, which speeds up some common operations.  In particular it
      enables us to avoid costly indirect jumps in many cases.
      
      More information in the commentary:
      
      http://hackage.haskell.org/trac/ghc/wiki/Commentary/Rts/HaskellExecution/PointerTagging
      6015a94f
  3. 26 Jul, 2007 13 commits
  4. 25 Jul, 2007 10 commits
  5. 24 Jul, 2007 1 commit
    • Simon Marlow's avatar
      hs_exit()/shutdownHaskell(): wait for outstanding foreign calls to complete before returning · 681aad99
      Simon Marlow authored
      This is pertinent to #1177.  When shutting down a DLL, we need to be
      sure that there are no OS threads that can return to the code that we
      are about to unload, and previously the threaded RTS was unsafe in
      this respect.
      
      When exiting a standalone program we don't have to be quite so
      paranoid: all the code will disappear at the same time as any running
      threads.  Happily exiting a program happens via a different path:
      shutdownHaskellAndExit().  If we're about to exit(), then there's no
      need to wait for foreign calls to complete.
      681aad99
  6. 23 Jul, 2007 1 commit
  7. 22 Jul, 2007 1 commit
  8. 24 Jul, 2007 1 commit
  9. 23 Jul, 2007 1 commit
  10. 22 Jul, 2007 3 commits
  11. 21 Jul, 2007 1 commit
  12. 20 Jul, 2007 1 commit
  13. 21 Jul, 2007 2 commits
  14. 19 Jul, 2007 2 commits
  15. 06 Jul, 2007 1 commit
    • Clemens Fruhwirth's avatar
      Fix -split-obj on Mac OS via -fasm · ee40dd6b
      Clemens Fruhwirth authored
      The problem of the splitter was that it re-emitted section directives
      for every dynamic label found. The following was torn apart
      
      .symbol_stubs
      .indirect <symbol>
      L_<symbol>$stub: 
      	jmp *...
      L_<symbol>$stub_binder:
      	..somebinding code..
      
      into
      
      .symbol_stubs
      .indirect_symbol <symbol>
      L_<symbol>$stub: 
      	jmp *...
      .symbol_stubs <--- NEW
      L_<symbol>$stub_binder:
      	..somebinding code..
      
      This is incorrect as the Mac OS assembler enforces that every new code
      section that goes into .symbol_stubs is associated with the linker
      directive .indirect_symbol. This sanity check is obviously violated
      when we reemit .symbol_stub in the splitter. The solution is to ignore
      everything that ends with $stub_binder as new label, and chuck it into
      a single label for $stub.
      
      Also the splitter has to recognize .section __DATA... for the lazy_ptr
      indirection symbol. Adds a reminder to PositionIndependentCode.hs to
      take care of the splitter when the code generation is changed.
      
      This should not affect -fvia-c as the code generated by the C compiler
      is entirely different.
      ee40dd6b