1. 12 Sep, 2008 1 commit
  2. 10 Sep, 2008 1 commit
  3. 15 Sep, 2008 1 commit
  4. 14 Sep, 2008 1 commit
  5. 15 Sep, 2008 1 commit
  6. 14 Sep, 2008 1 commit
  7. 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
  8. 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
  9. 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
  10. 13 Aug, 2008 1 commit
  11. 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
  12. 31 Jul, 2008 1 commit
  13. 05 Aug, 2008 1 commit
  14. 30 Jul, 2008 1 commit
  15. 22 Jul, 2008 2 commits
  16. 20 Jul, 2008 3 commits
  17. 11 Jul, 2008 1 commit
  18. 12 Jul, 2008 1 commit
  19. 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
  20. 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
  21. 05 Jul, 2008 1 commit
  22. 02 Jul, 2008 1 commit
  23. 16 Jun, 2008 2 commits
    • simonpj@microsoft.com's avatar
      Fix Trac #2321: bug in SAT · c3693c2d
      simonpj@microsoft.com authored
        This is a fairly substantial rewrite of the Static Argument Transformatoin,
        done by Max Bolingbroke and reviewed and modified by Simon PJ.
        
        * Fix a subtle scoping problem; see Note [Binder type capture]
        * Redo the analysis to use environments
        * Run gentle simlification just before the transformation
      c3693c2d
    • Ian Lynagh's avatar
      More commandline flag improvements · 0f5e104c
      Ian Lynagh authored
      * Allow -ffoo flags to be deprecated
      * Mark some -ffoo flags as deprecated
      * Avoid using deprecated flags in error messages, in the build system, etc
      * Add a flag to en/disable the deprecated flag warning
      0f5e104c
  24. 15 Jun, 2008 1 commit
  25. 14 Jun, 2008 5 commits
  26. 06 Jun, 2008 1 commit
  27. 03 Jun, 2008 1 commit
    • Simon Marlow's avatar
      New flag: -dno-debug-output · 667ef993
      Simon Marlow authored
      From the docs:
         <para>Suppress any unsolicited debugging output.  When GHC
           has been built with the <literal>DEBUG</literal> option it
           occasionally emits debug output of interest to developers.
           The extra output can confuse the testing framework and
           cause bogus test failures, so this flag is provided to
           turn it off.</para>
      667ef993
  28. 30 May, 2008 1 commit
  29. 23 May, 2008 1 commit