Re: Elisp native profiler

[Stefan Monnier]

> If the overhead can be avoided when not profiling (e.g., depending on
> some global variable), that would be acceptable, I think.

No, I think some of the overhead can't be chosen at runtime (e.g. the
`struct backtrace' will always use up stack space), and adding a test on
a global variable to functions like `car' doesn't sound like
a good idea.
IOW I don't want to add it flat out to all DEFUN functions.  To some of
them, yes, th, and to some non-DEFUN functions as well.


        Stefan