#4414: scc001 fails: one SCC entered 0 times; another not mentioned when
optimisation is on
---------------------------------+------------------------------------------
Reporter: igloo | Owner: simonmar
Type: bug | Status: new
Priority: normal | Milestone: 7.0.2
Component: Profiling | Version: 6.12.3
Keywords: | Testcase:
Blockedby: | Difficulty:
Os: Unknown/Multiple | Blocking:
Architecture: Unknown/Multiple | Failure: None/Unknown
---------------------------------+------------------------------------------
Comment(by simonmar):
Getting the entry counts right adds more constraints to what we can do
with SCCs, and I think might end up costing quite a lot. e.g. in the
example above we have
{{{
let x = scc "g" y
}}}
and if it weren't for the entry count we could eliminate it altogether
(the bug is that we are compiling this closure as a standard form when it
shouldn't be, but I bet there are other similar bugs in this area).
Arguably HPC is a better way to get this information. I tentatively
propose that we dispense with entry counts in the profiler.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/4414#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
