Re: [Emacs-diffs] /srv/bzr/emacs/trunk r110342: Count overruns when profiling; change units to ns.

[Paul Eggert]

On 10/03/2012 10:18 AM, Eli Zaretskii wrote:

> imagine that 30% of the elapsed time that passed while profiling
> Emacs got very little or no CPU time

It's supposed to be a CPU time profiler, so that shouldn't
be a problem.  Granted, hosts that don't profile CPU time
(and where we fall back on real-time) will provide inaccurate
numbers in that situation, but they're already way-inaccurate
so it doesn't really matter.

> So how about a new primitive that would return the information from
> clock_gettime (or getrusage, if clock_gettime is not available), which
> profiler.el could then use to convert timer ticks into seconds?

That should work.  I would like to add an optional argument
to current-time, to specify which clock we want.  But isn't
this sort of thing something that we need to delay until later?
Aren't we in a feature freeze?