But maybe we should just give up, since CPUTime is not part of the Haskell report anymore. Keep the function cpuTimePrecision for backward compatibility, but change the docstring to say what it really does: return

#2140: cpuTimePrecision is wrong -------------------------------------+------------------------------------- Reporter: guest | Owner: Type: bug | Status: new Priority: lowest | Milestone: Component: Core Libraries | Version: 6.8.2 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Documentation | Unknown/Multiple bug | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by bgamari): the number of picoseconds between clock ticks. This sounds reasonable to me. For the record, I believe the relevant Linux interface here is `clock_getres` (which itself only has nanosecond resolution at best). -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/2140#comment:19 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler