#437: Recompilation check should include flags
-----------------------+----------------------------------------------------
  Reporter:  simonpj   |          Owner:  dterei          
      Type:  bug       |         Status:  new             
  Priority:  low       |      Milestone:  7.2.1           
 Component:  Compiler  |        Version:  6.4.1           
Resolution:  None      |       Keywords:                  
  Testcase:  mod175    |      Blockedby:                  
Difficulty:  Unknown   |             Os:  Unknown/Multiple
  Blocking:            |   Architecture:  Unknown/Multiple
   Failure:  Other     |  
-----------------------+----------------------------------------------------

Comment(by igloo):

 Flag ordering is important (e.g. `-O0 -O` is not the same as `-O -O0`).
 Also, some flags are equivalent to others.

 Rather than storing the set of flags (`-O` etc), it might be better to use
 the set of enabled `DynFlag`s (`Opt_Specialise` etc) and `ExtensionFlag`s.

 It might also make sense to split `DynFlag` into 2 (or more) types, so
 e.g. `Opt_D_dump*` and `Opt_Warn*` are in a different type than the flags
 that actually affect optimisation etc. Then the recompilation checker can
 just look at the set of values of the second type (and the `ExtensionFlag`
 type). That may mean it sometimes recompiles when it isn't strictly
 necessary, but I don't think that's a major problem.

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/437#comment:20>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler

_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to