1. 05 Aug, 2009 1 commit
  2. 03 Aug, 2009 8 commits
  3. 02 Aug, 2009 1 commit
  4. 04 Aug, 2009 1 commit
  5. 03 Aug, 2009 5 commits
  6. 02 Aug, 2009 1 commit
    • Simon Marlow's avatar
      RTS tidyup sweep, first phase · a2a67cd5
      Simon Marlow authored
      The first phase of this tidyup is focussed on the header files, and in
      particular making sure we are exposinng publicly exactly what we need
      to, and no more.
       - Rts.h now includes everything that the RTS exposes publicly,
         rather than a random subset of it.
       - Most of the public header files have moved into subdirectories, and
         many of them have been renamed.  But clients should not need to
         include any of the other headers directly, just #include the main
         public headers: Rts.h, HsFFI.h, RtsAPI.h.
       - All the headers needed for via-C compilation have moved into the
         stg subdirectory, which is self-contained.  Most of the headers for
         the rest of the RTS APIs have moved into the rts subdirectory.
       - I left MachDeps.h where it is, because it is so widely used in
         Haskell code.
       - I left a deprecated stub for RtsFlags.h in place.  The flag
         structures are now exposed by Rts.h.
       - Various internal APIs are no longer exposed by public header files.
       - Various bits of dead code and declarations have been removed
       - More gcc warnings are turned on, and the RTS code is more
       - More source files #include "PosixSource.h", and hence only use
         standard POSIX (1003.1c-1995) interfaces.
      There is a lot more tidying up still to do, this is just the first
      pass.  I also intend to standardise the names for external RTS APIs
      (e.g use the rts_ prefix consistently), and declare the internal APIs
      as hidden for shared libraries.
  7. 27 Jul, 2009 1 commit
  8. 28 Jun, 2009 1 commit
  9. 03 Aug, 2009 1 commit
  10. 02 Aug, 2009 1 commit
  11. 01 Aug, 2009 1 commit
  12. 24 Jul, 2009 4 commits
  13. 06 Jul, 2009 1 commit
  14. 01 Jul, 2009 2 commits
  15. 30 Jun, 2009 1 commit
  16. 27 Jun, 2009 1 commit
  17. 24 Jun, 2009 1 commit
  18. 22 Jun, 2009 1 commit
  19. 16 Jun, 2009 1 commit
  20. 13 Jun, 2009 3 commits
  21. 11 Jun, 2009 1 commit
  22. 13 Jun, 2009 1 commit
  23. 12 Jun, 2009 1 commit
    • Duncan Coutts's avatar
      Add and export rts_unsafeGetMyCapability from rts · 85df606a
      Duncan Coutts authored
      We need this, or something equivalent, to be able to implement
      stgAllocForGMP outside of the rts. That's because we want to use
      allocateLocal which allocates from the given capability without
      having to take any locks. In the gmp primops we're basically in
      an unsafe foreign call, that is a context where we hold a current
      capability. So it's safe for us to use allocateLocal. We just
      need a way to get the current capability. The method to get the
      current capability varies depends on whether we're using the
      threaded rts or not. When stgAllocForGMP is built inside the rts
      that's ok because we can do it conditionally on THREADED_RTS.
      Outside the rts we need a single api we can call without knowing
      if we're talking to a threaded rts or not, hence this addition.