#5282: Bizarre results from -P profiler on OS X
------------------------------------------+---------------------------------
Reporter: bos | Owner: simonmar
Type: bug | Status: closed
Priority: high | Milestone: 7.4.1
Component: Runtime System | Version: 7.0.3
Resolution: fixed | Keywords:
Testcase: | Blockedby:
Difficulty: | Os: Unknown/Multiple
Blocking: | Architecture: x86_64 (amd64)
Failure: Incorrect result at runtime |
------------------------------------------+---------------------------------
Changes (by simonmar):
* status: new => closed
* resolution: => fixed
Comment:
commit 6b1098511aaabd2c9503ee7be6da1944466f9cb4
{{{
Author: Simon Marlow <[email protected]>
Date: Fri Nov 25 13:11:39 2011 +0000
Time handling overhaul
Terminology cleanup: the type "Ticks" has been renamed "Time", which
is an StgWord64 in units of TIME_RESOLUTION (currently nanoseconds).
The terminology "tick" is now used consistently to mean the interval
between timer signals.
The ticker now always ticks in realtime (actually CLOCK_MONOTONIC if
we have it). Before it used CPU time in the non-threaded RTS and
realtime in the threaded RTS, but I've discovered that the CPU timer
has terrible resolution (at least on Linux) and isn't much use for
profiling. So now we always use realtime. This should also fix
The default tick interval is now 10ms, except when profiling where we
drop it to 1ms. This gives more accurate profiles without affecting
runtime too much (<1%).
Lots of cleanups - the resolution of Time is now in one place
only (Rts.h) rather than having calculations that depend on the
resolution scattered all over the RTS. I hope I found them all.
}}}
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/5282#comment:20>
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
