1. 27 Nov, 2007 1 commit
  2. 16 Nov, 2007 1 commit
  3. 09 Oct, 2007 1 commit
  4. 21 Sep, 2007 1 commit
  5. 04 Sep, 2007 1 commit
  6. 03 Sep, 2007 1 commit
  7. 01 Sep, 2007 1 commit
  8. 07 Aug, 2007 1 commit
  9. 17 Jul, 2007 1 commit
  10. 08 Jul, 2007 1 commit
  11. 02 Jul, 2007 1 commit
  12. 27 Jun, 2007 1 commit
  13. 26 Jun, 2007 1 commit
  14. 22 Jun, 2007 2 commits
  15. 12 Jun, 2007 1 commit
    • Ian Lynagh's avatar
      Tweak banner printing · cedd4187
      Ian Lynagh authored
      * -{short,long}-ghci-banner are now dynamic options, so you can put
        ":set -short-ghci-banner" in .ghci
      * The -v2 banner information now always tells you what compiler booted GHC,
        and what stage the compiler is. Thus we no longer assume that stage > 1
        iff GHCI is defined.
      cedd4187
  16. 01 Jun, 2007 1 commit
  17. 10 May, 2007 1 commit
  18. 07 May, 2007 1 commit
  19. 04 May, 2007 1 commit
    • simonpj@microsoft.com's avatar
      Make -frewrite-rules into a dynamic flag; off for -O0 · 5943ce90
      simonpj@microsoft.com authored
      Argubly rewrite rules should not fire with -O0, and it turns
      out that when compiling GHC.Base with -O0 we get a crash if
      the rewrite rules do fire (see Note [Scoping for Builtin rules]
      in PrelRules).
      
      So unless someone yells, rewrite rules are off with -O0.
      
      The new (now dynamic) flag is 
          -frewrite rules (with -fno-rewrite-rules to disable)
      
      The old (static) flag -frules-off is gone.
      5943ce90
  20. 01 May, 2007 1 commit
    • chevalier@alum.wellesley.edu's avatar
      Remove references to -fticky-ticky flag · 3c506a6c
      chevalier@alum.wellesley.edu authored
      -ticky is the command-line flag for ticky-ticky profiling now, but
      internally, the -fticky-ticky flag was used to represent whether ticky
      was on. This led to link errors if the user supplied -fticky-ticky but
      not -ticky (ticky code would be generated but the wrong RTS library
      would be passed to the linker). I removed references to -fticky-ticky
      -- now, only the way flags dictate whether ticky is on, and
      -fticky-ticky is no longer accepted as a command-line option.
      3c506a6c
  21. 14 Apr, 2007 1 commit
  22. 06 Apr, 2007 1 commit
  23. 09 Feb, 2007 1 commit
  24. 07 Feb, 2007 1 commit
    • chevalier@alum.wellesley.edu's avatar
      Lightweight ticky-ticky profiling · 5ddee764
      chevalier@alum.wellesley.edu authored
      The following changes restore ticky-ticky profiling to functionality
      from its formerly bit-rotted state. Sort of. (It got bit-rotted as part
      of the switch to the C-- back-end.)
      
      The way that ticky-ticky is supposed to work is documented in Section 5.7
      of the GHC manual (though the manual doesn't mention that it hasn't worked
      since sometime around 6.0, alas). Changes from this are as follows (which
      I'll document on the wiki):
      
      * In the past, you had to build all of the libraries with way=t in order to
      use ticky-ticky, because it entailed a different closure layout. No longer.
      You still need to do make way=t in rts/ in order to build the ticky RTS,
      but you should now be able to mix ticky and non-ticky modules.
      
      * Some of the counters that worked in the past aren't implemented yet.
      I was originally just trying to get entry counts to work, so those should
      be correct. The list of counters was never documented in the first place,
      so I hope it's not too much of a disaster that some don't appear anymore.
      Someday, someone (perhaps me) should document all the counters and what 
      they do. For now, all of the counters are either accurate (or at least as
      accurate as they always were), zero, or missing from the ticky profiling
      report altogether.
      
      This hasn't been particularly well-tested, but these changes shouldn't
      affect anything except when compiling with -fticky-ticky (famous last
      words...)
      
      Implementation details:
      
      I got rid of StgTicky.h, which in the past had the macros and declarations 
      for all of the ticky counters. Now, those macros are defined in Cmm.h.
      StgTicky.h was still there for inclusion in C code. Now, any remaining C
      code simply cannot call the ticky macros -- or rather, they do call those
      macros, but from the perspective of C code, they're defined as no-ops. 
      (This shouldn't be too big a problem.)
      
      I added a new file TickyCounter.h that has all the declarations for ticky
      counters, as well as dummy macros for use in C code. Someday, these 
      declarations should really be automatically generated, since they need
      to be kept consistent with the macros defined in Cmm.h.
      
      Other changes include getting rid of the header that was getting added to
      closures before, and getting rid of various code having to do with eager
      blackholing and permanent indirections (the changes under compiler/ 
      and rts/Updates.*).
      5ddee764
  25. 11 Jan, 2007 1 commit
  26. 09 Dec, 2006 1 commit
  27. 07 Dec, 2006 1 commit
    • wolfgang.thaller@gmx.net's avatar
      x86_64: support PIC and therefore, Mac OS X in the NCG · 28c556a5
      wolfgang.thaller@gmx.net authored
      Supporting x86_64-apple-darwin in the NCG basically boils down to supporting
      position-independent code in the NCG.
      PIC code works almost exactly the same as on x86_64-linux, while position-dependent
      code is not supported at all.
      This patch implements -fPIC for x86_64-linux, too, but that is untested.
      
      28c556a5
  28. 02 Nov, 2006 1 commit
  29. 23 Oct, 2006 1 commit
  30. 17 Oct, 2006 1 commit
  31. 11 Oct, 2006 1 commit
  32. 05 Oct, 2006 1 commit
  33. 03 Oct, 2006 1 commit
  34. 04 Oct, 2006 3 commits
  35. 06 Sep, 2006 1 commit
  36. 24 Aug, 2006 1 commit
  37. 11 Aug, 2006 1 commit