#5928: INLINABLE fails to specialize in presence of simple wrapper
---------------------------------+------------------------------------------
Reporter: tibbe | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Compiler | Version: 7.4.1
Keywords: | Os: Unknown/Multiple
Architecture: Unknown/Multiple | Failure: None/Unknown
Difficulty: Unknown | Testcase:
Blockedby: | Blocking:
Related: |
---------------------------------+------------------------------------------
Comment(by tibbe):
Replying to [comment:8 simonpj]:
> Maybe so, but it ''still'' depends on the fragile property that `(!)` is
inlined.
True, but I don't think that's such a big deal. The surprising thing here
is that `lookup` doesn't get specialized even though `(!)` is inlined.
I think it's reasonable to expect uses to understand that if a function is
large it might not get inlined and thus some optimization might not be
exposed. It might even be reasonable to expect some optimizations to not
fire if you manually delay inlining to some later phase. What is a bit
unreasonable is that optimizations don't happen when things are expected
to (and do) inline as early as they possibly could.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/5928#comment:9>
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
