#5779: SPECIALISE pragma generates wrong activations
--------------------------------------+-------------------------------------
Reporter: rl | Owner:
Type: bug | Status: closed
Priority: normal | Milestone:
Component: Compiler | Version: 7.5
Resolution: invalid | Keywords:
Os: Unknown/Multiple | Architecture: Unknown/Multiple
Failure: Runtime performance bug | Difficulty: Unknown
Testcase: | Blockedby:
Blocking: | Related:
--------------------------------------+-------------------------------------
Comment(by simonpj):
* Yes, we really need a way to say "ALWAYS". And we don't have that at
the moment; you'd have to say "[100]" or something. (Which means phase
100 and later.) I'm not sure that's it's worth the pain of adding an
ALWAYS case too.
* There is no guarantee about SPECIALISE vs INLINE. After all, if you
are going to inline something that is ''even better'' than specialising
it. Generally you want specialisation to kick in only if inlining
doesn't. So in the case you give, I'd just nuke the SPECIALISE pragma.
Unless you specifically want to SPECIALISE first, in which case give a
phase.
Simon
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/5779#comment:4>
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
