1. 12 Apr, 2008 1 commit
  2. 29 Mar, 2008 1 commit
  3. 25 Mar, 2008 1 commit
  4. 07 Feb, 2008 1 commit
    • Ian Lynagh's avatar
      Convert more UniqFM's back to LazyUniqFM's · d51f42f6
      Ian Lynagh authored
      These fix these failures:
         break008(ghci)
         break009(ghci)
         break026(ghci)
         ghci.prog009(ghci)
         ghci025(ghci)
         print007(ghci)
         prog001(ghci)
         prog002(ghci)
         prog003(ghci)
      at least some of which have this symptom:
          Exception: expectJust prune
      d51f42f6
  5. 12 Dec, 2007 1 commit
  6. 17 Jan, 2008 1 commit
  7. 16 Jan, 2008 1 commit
  8. 10 Jan, 2008 1 commit
  9. 16 Jan, 2008 1 commit
  10. 10 Jan, 2008 1 commit
  11. 12 Jan, 2008 2 commits
  12. 02 Jan, 2008 1 commit
  13. 25 Dec, 2007 1 commit
    • chevalier@alum.wellesley.edu's avatar
      Extend API for compiling to and from Core · 98c68a1c
      chevalier@alum.wellesley.edu authored
      Added API support for compiling Haskell to simplified Core, and for
      compiling Core to machine code. The latter, especially, should be
      considered experimental and has only been given cursory testing. Also
      fixed warnings in DriverPipeline. Merry Christmas.
      98c68a1c
  14. 26 Sep, 2007 1 commit
  15. 23 Sep, 2007 2 commits
  16. 21 Sep, 2007 1 commit
  17. 12 Sep, 2007 1 commit
  18. 31 Aug, 2007 1 commit
  19. 10 Sep, 2007 1 commit
  20. 11 Sep, 2007 1 commit
  21. 05 Sep, 2007 1 commit
    • Simon Marlow's avatar
      FIX #1650: ".boot modules interact badly with the ghci debugger" · e2782137
      Simon Marlow authored
      In fact hs-boot files had nothing to do with it: the problem was that
      GHCi would forget the breakpoint information for a module that had
      been reloaded but not recompiled.  It's amazing that we never noticed
      this before.
      
      The ModBreaks were in the ModDetails, which was the wrong place.  When
      we avoid recompiling a module, ModDetails is regenerated from ModIface
      by typecheckIface, and at that point it has no idea what the ModBreaks
      should be, so typecheckIface made it empty.  The right place for the
      ModBreaks to go is with the Linkable, which is retained when
      compilation is avoided.  So now I've placed the ModBreaks in with the
      CompiledByteCode, which also makes it clear that only byte-code
      modules have breakpoints.
      
      This fixes break022/break023
      e2782137
  22. 04 Sep, 2007 2 commits
  23. 03 Sep, 2007 1 commit
  24. 01 Sep, 2007 1 commit
  25. 21 Aug, 2007 1 commit
  26. 10 Aug, 2007 1 commit
    • Simon Marlow's avatar
      FIX #1271: create manifests, and embed them in executables on Windows · eb4352ab
      Simon Marlow authored
      We have 4 new flags:
      
        -fno-gen-manifest
           suppresses creation of foo.exe.manifest
      
        -fno-embed-manifest
           suppresses embedding of the manifest in the executable
      
        -pgmwindres
           specify a program to use instead of windres
      
        -optwindres
           extra options to pass to windres
      
      "windres" is now copied from mingw and included in a binary
      distribution.
      eb4352ab
  27. 21 Aug, 2007 1 commit
    • Simon Marlow's avatar
      FIX #1427, #1569: gcc 4.2.x needs -fno-toplevel-reorder · 2ebe8add
      Simon Marlow authored
      We now have various flags that need to be passed to gcc, but only if
      the local gcc version supports them.  So instead of wiring this
      knowledge into ghc when it is built, we now put these "extra gcc
      flags" into a text file in $libdir, extra-gcc-flags, which is created
      by configure.  It is also created by the configure script of a binary
      distribution, so a binary dist is independent of the gcc version used
      to build it.
      
      Hopefully I got the binary-dist stuff right, but binary dists aren't
      currently working so we'll need to come back and check this.
      2ebe8add
  28. 07 Aug, 2007 1 commit
  29. 03 Aug, 2007 1 commit
    • Simon Marlow's avatar
      FIX part of #1372, improvements to the recompilation checker · de21f53e
      Simon Marlow authored
      This patch adds a check that each imported module is listed in
      the dependencies from the previous interface.  It catches the
      following cases and forces recompilation:
         - an exposed package has been upgraded
         - we are compiling with different package flags
         - a home module that was shadowing a package module has been removed
         - a new home module has been added that shadows a package module
      
      I haven't yet added the package timestamping as described in #1372.
      de21f53e
  30. 01 Aug, 2007 1 commit
  31. 17 Jul, 2007 1 commit
  32. 19 Jul, 2007 1 commit
  33. 27 Jun, 2007 2 commits
  34. 10 May, 2007 1 commit
  35. 16 Apr, 2007 1 commit
  36. 11 Apr, 2007 1 commit
    • Simon Marlow's avatar
      Rationalise GhcMode, HscTarget and GhcLink · 3c22606b
      Simon Marlow authored
      This patch cleans up the GHC API, and adds some functionality: we can
      now compile to object code inside GHCi.
      
      Previously we had:
      
        data GhcMode
          = BatchCompile
          | Interactive
          | OneShot
          | JustTypecheck
          | MkDepend
        
        data HscTarget
          = HscC
          | HscAsm
          | HscJava
          | HscInterpreted
          | HscNothing
      
      There was redundancy here; if GhcMode is Interactive, then only
      HscInterpreted makes sense, and JustTypecheck required HscNothing.
      Now we have:
      
        data GhcMode
          = CompManager       -- ^ --make, GHCi, etc.
          | OneShot           -- ^ ghc -c Foo.hs
          | MkDepend          -- ^ ghc -M, see Finder for why we need this
      
      and HscTarget remains as before.
      
      Previously GhcLink looked like this:
      
        data GhcLink = NoLink | StaticLink
      
      Now we have:
      
        data GhcLink = NoLink | LinkBinary | LinkInMemory
      
      The idea being that you can have an HscTarget of HscAsm (for example)
      and still link in memory.
      
      There are two new flags:
      
        -fobject-code selects object code as the target (selects
                      either -fasm or -fvia-C, whichever is the default)
                      This can be usd with ':set' in GHCi, or on the command line.
      
        -fbyte-code   sets byte-code as the target.  Only works in GHCi.
                      One day maybe this could save the byte code in a file
                      when used outside GHCi.
      
        (names chosen for consistency with -fno-code).
      
      Changes to the GHC API: newSession no longer takes the GhcMode
      argument.  The GhcMode defaults to CompManager, which is usually what
      you want.  To do JustTypecheck now, just set hscTarget to HscNothing.
      3c22606b