#437: Recompilation check should include flags
-----------------------+----------------------------------------------------
Reporter: simonpj | Owner: dterei
Type: bug | Status: new
Priority: low | Milestone: 7.4.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 dterei):
So I'm finally actually working on this. There are some questions though:
- Should optmisation flag changes be candidates for recompilation?
- There is the whole hierarchy of hashes GHC uses (Interface File Hash,
ABI Hash and then individual more specialised hashes). I've created a new
flags hash. Should the ABI and Interface File Hash be dependent on the
flags hash? The interface file hash should be. However I think for the ABI
hash we could do something a little more complex if its worth the effort.
There are probably some flags that if changed we want it to trigger a
recompilation of the module M but we don't want the modules ABI hash to
change and trigger recompilation of modules depending on M. However some
flags like '--main-is' should change M's ABI hash. Is it worth
differentiating between these two flag cases?
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/437#comment:23>
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
