#4428: Local functions lose their unfoldings
---------------------------------+------------------------------------------
Reporter: rl | Owner:
Type: bug | Status: merge
Priority: normal | Milestone: 7.0.2
Component: Compiler | Version: 7.1
Keywords: | Testcase:
Blockedby: | Difficulty:
Os: Unknown/Multiple | Blocking:
Architecture: Unknown/Multiple | Failure: Runtime performance bug
---------------------------------+------------------------------------------
Comment(by rl):
Replying to [comment:11 simonpj]:
> Replying to [comment:10 rl]:
>
> Lets just deal with this first. When I said that the change was
"invisible" I meant that it had no observable effect. The only difference
(I believe) is that if you say `INLINE[n]` then the rhs-to-be-inlined gets
optimised with phase=n (only). I suppose that potentially might save a bit
of work at the inline site. Is that what you mean?
Probably. I'm not sure. I don't think this is too important.
> I don't understand what you mean by the previous semantics being much
cleaner. The semantics hasn't changed, I believe. Do you think it has?
I think I just liked reading the Core (including unfoldings) generated
previously more as compared to now. By "semantics" I just mean the
behaviour of the various transformations, not the semantics of the
program.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/4428#comment:12>
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
