1. 14 Oct, 2008 1 commit
  2. 01 Oct, 2008 1 commit
  3. 02 Oct, 2008 1 commit
    • rl@cse.unsw.edu.au's avatar
      Prevent excessive inlining with DPH · 444c6250
      rl@cse.unsw.edu.au authored
      This adds a new flag -finline-if-enough-args which disables inlining for
      partially applied functions. It is automatically set by -Odph. This is a
      temporary hack and should remain undocumented.
      
      MERGE TO 6.10
      444c6250
  4. 27 Sep, 2008 1 commit
  5. 25 Sep, 2008 1 commit
  6. 23 Sep, 2008 1 commit
  7. 22 Sep, 2008 1 commit
  8. 18 Sep, 2008 2 commits
    • pepe's avatar
      Fix a couple of issues with :print · decbb181
      pepe authored
            
            - Ticket #1995: Unsoundness with newtypes
            - Ticket #2475: "Can't unify" error when stopped at an exception
            
            In addition this patch adds the following:
            
            - Unfailingness: RTTI cannot panic anymore. 
              In case of failure, it recovers gracefully by returning the "I know nothing" type
            - A -ddump-rtti flag
      decbb181
    • Jedai's avatar
      RichTokenStream support · 36104d7a
      Jedai authored
      This patch adds support for raw token streams, that contain more
      information than normal token streams (they contains comments at
      least). The "lexTokenStream" function brings this support to the
      Lexer module. In addition to that, functions have been added to
      the GHC module to make easier to recover of the token stream of 
      a module ("getTokenStream").
      
      Building on that, I added what could be called "rich token
      stream": token stream to which have been added the source string
      corresponding to each token, the function addSourceToToken takes
      a StringBuffer and a starting SrcLoc and a token stream and build
      this rich token stream. getRichTokenStream is a convenience
      function to get a module rich token stream. "showRichTokenStream"
      use the SrcLoc information in such a token stream to get a string
      similar to the original source (except unsignificant
      whitespaces). Thus "putStrLn . showRichTokenStream =<<
      getRichTokenStream s mod" should print a valid module source, the
      interesting part being to modify the token stream between the get
      and the show of course.
      36104d7a
  9. 17 Sep, 2008 2 commits
  10. 16 Sep, 2008 2 commits
  11. 12 Sep, 2008 1 commit
  12. 10 Sep, 2008 1 commit
  13. 15 Sep, 2008 1 commit
  14. 14 Sep, 2008 1 commit
  15. 15 Sep, 2008 1 commit
  16. 14 Sep, 2008 1 commit
  17. 10 Sep, 2008 1 commit
    • simonpj@microsoft.com's avatar
      Robustify the setting of implied flags · 3998d13f
      simonpj@microsoft.com authored
      When setting implied flags, do so recursively.  So if -Xa implies -Xb,
      and -Xb implies -Xc, we do the right thing. 
      
      I thought we needed this, but we don't.  But it seems like a good idea
      anyway.
      3998d13f
  18. 26 Aug, 2008 3 commits
    • Ian Lynagh's avatar
      Give locations of flag warnings/errors · fc9bbbab
      Ian Lynagh authored
      fc9bbbab
    • Ian Lynagh's avatar
      Remove a now-redundant comment · 54280054
      Ian Lynagh authored
      54280054
    • simonpj@microsoft.com's avatar
      Fix flaggery for RULES (cf Trac #2497) · 24b1e136
      simonpj@microsoft.com authored
      This patch executes the plan described in the discussion in Trac #2497.
      Specficially:
      
          * Inside a RULE, switch on the forall-as-keyword in the lexer,
            unconditionally. (Actually this is done by an earlier patch.)
      
          * Merge the -XScopedTypeVariables and -XPatternSignatures flags,
            and deprecate the latter. Distinguishing them isn't senseless,
            but it's jolly confusing.
      
          * Inside a RULE, switch on -XScopedTypeVariables unconditionally. 
      
          * Change -frewrite-rules to -fenable-rewrite-rules; deprecate the former. 
            Internally the DynFlag is now Opt_EnableRewriteRules.
      
      There's a test in typecheck/should_compile/T2497.hs
      24b1e136
  19. 12 Aug, 2008 1 commit
    • Simon Marlow's avatar
      put back -fwarn-depcrecations · 27abb1f5
      Simon Marlow authored
      It was replaced by -fwarn-warnings-deprecations, but I think we want
      to keep it for backwards compatibility.  I'm not sure we want to
      deprecate it either...
      27abb1f5
  20. 13 Aug, 2008 1 commit
  21. 05 Aug, 2008 1 commit
    • Simon Marlow's avatar
      Add -XPackageImports, new syntax for package-qualified imports · 1867a7bb
      Simon Marlow authored
      Now you can say
        
        import "network" Network.Socket
      
      and get Network.Socket from package "network", even if there are
      multiple Network.Socket modules in scope from different packages
      and/or the current package.
      
      This is not really intended for general use, it's mainly so that we
      can build backwards-compatible versions of packages, where we need to
      be able to do
      
      module GHC.Base (module New.GHC.Base) where
      import "base" GHC.Base as New.GHC.Base
      1867a7bb
  22. 31 Jul, 2008 1 commit
  23. 05 Aug, 2008 1 commit
  24. 30 Jul, 2008 1 commit
  25. 22 Jul, 2008 2 commits
  26. 20 Jul, 2008 3 commits
  27. 11 Jul, 2008 1 commit
  28. 12 Jul, 2008 1 commit
  29. 09 Jul, 2008 2 commits
    • Ian Lynagh's avatar
      Remove all references to -mno-cygwin · ccc9a4a5
      Ian Lynagh authored
      We shouldn't need it, as we don't call cygwin's gcc, and it was causing
      problems with the nightly builders passing it to GHC.
      ccc9a4a5
    • Simon Marlow's avatar
      add -fwarn-dodgy-foreign-imports (see #1357) · 3b6382e4
      Simon Marlow authored
      From the entry in the User's guide:
      
      -fwarn-dodgy-foreign-imports causes a warning to be emitted for
      foreign imports of the following form:
      
      foreign import "f" f :: FunPtr t
      
      on the grounds that it probably should be
      
      foreign import "&f" f :: FunPtr t
      
      The first form declares that `f` is a (pure) C function that takes no
      arguments and returns a pointer to a C function with type `t`, whereas
      the second form declares that `f` itself is a C function with type
      `t`.  The first declaration is usually a mistake, and one that is hard
      to debug because it results in a crash, hence this warning.
      3b6382e4
  30. 08 Jul, 2008 1 commit
    • Ian Lynagh's avatar
      Extend the flag for not automatically linking haskell98 · 53ec704b
      Ian Lynagh authored
      It now also doesn't automatically link base and rts either.
      We need this when we've done a build, so base and rts are in the
      package.conf, but we've then cleaned the libraries so they don't
      physically exist any more.
      53ec704b
  31. 05 Jul, 2008 1 commit