This project is mirrored from https://gitlab.haskell.org/ghc/ghc.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
  1. 26 Apr, 2007 1 commit
    • mnislaih's avatar
      Dont tidy up tyvars after :print type reconstruction · cdfe9b08
      mnislaih authored
      I introduced a bug yesterday when I changed the way tidying up was performed.
      As a result of tidying,  cvObtainTerm could be returning types 
      with regular tyvars inside, which never should.
      
      But actually, it's better if we do not do the tidying up, in order to 
      keep the tyvar names from the environment.
      New names will be introduced only when an existential is found, which
      is not so common. In this case the user will see a funny name. 
      Is that really an issue?
      cdfe9b08
  2. 25 Apr, 2007 4 commits
  3. 24 Apr, 2007 1 commit
  4. 20 Apr, 2007 2 commits
  5. 19 Apr, 2007 2 commits
  6. 14 Apr, 2007 1 commit
  7. 17 Apr, 2007 1 commit
    • Simon Marlow's avatar
      Re-working of the breakpoint support · cdce6477
      Simon Marlow authored
      This is the result of Bernie Pope's internship work at MSR Cambridge,
      with some subsequent improvements by me.  The main plan was to
      
       (a) Reduce the overhead for breakpoints, so we could enable 
           the feature by default without incurrent a significant penalty
       (b) Scatter more breakpoint sites throughout the code
      
      Currently we can set a breakpoint on almost any subexpression, and the
      overhead is around 1.5x slower than normal GHCi.  I hope to be able to
      get this down further and/or allow breakpoints to be turned off.
      
      This patch also fixes up :print following the recent changes to
      constructor info tables.  (most of the :print tests now pass)
      
      We now support single-stepping, which just enables all breakpoints.
      
        :step <expr>     executes <expr> with single-stepping turned on
        :step            single-steps from the current breakpoint
      
      The mechanism is quite different to the previous implementation.  We
      share code with the HPC (haskell program coverage) implementation now.
      The coverage pass annotates source code with "tick" locations which
      are tracked by the coverage tool.  In GHCi, each "tick" becomes a
      potential breakpoint location.
      
      Previously breakpoints were compiled into code that magically invoked
      a nested instance of GHCi.  Now, a breakpoint causes the current
      thread to block and control is returned to GHCi.
      
      See the wiki page for more details and the current ToDo list:
      
        http://hackage.haskell.org/trac/ghc/wiki/NewGhciDebugger
      cdce6477
  8. 20 Feb, 2007 1 commit
    • bjpop@csse.unimelb.edu.au's avatar
      Constructor names in info tables · 7d6dffe5
      bjpop@csse.unimelb.edu.au authored
      This patch adds data constructor names into their info tables. 
      This is useful in the ghci debugger. It replaces the old scheme which
      was based on tracking data con names in the linker. 
      7d6dffe5
  9. 21 Feb, 2007 1 commit
  10. 16 Feb, 2007 1 commit
  11. 07 Feb, 2007 1 commit
  12. 21 Jan, 2007 1 commit
  13. 20 Jan, 2007 1 commit
  14. 07 Jan, 2007 1 commit
  15. 11 Jan, 2007 1 commit
  16. 07 Jan, 2007 1 commit
  17. 03 Jan, 2007 1 commit
  18. 20 Dec, 2006 1 commit
  19. 18 Dec, 2006 2 commits
  20. 10 Dec, 2006 1 commit
    • mnislaih's avatar
      Playing with closures · 2c92736e
      mnislaih authored
      RtClosureInspect includes a bunch of stuff for playing with closures:
      
      - the datatype Closure is the low level representation type
      - the datatype Term is the high level representation type
      - cvObtainTerm is the main entry point, providing the Term representation of an arbitrary closure
      2c92736e