[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Elisp native profiler
From: |
Eli Zaretskii |
Subject: |
Re: Elisp native profiler |
Date: |
Tue, 25 Sep 2012 22:10:30 +0200 |
> From: Stefan Monnier <address@hidden>
> Cc: address@hidden
> Date: Tue, 25 Sep 2012 13:28:37 -0400
>
> > Shouldn't profiling use the same framework as atimers
> > and the other async events?
>
> We could do that, but to the extent that it is possible to do all the
> work in the signal_handler while still being safe, I think it's
> preferable.
I bet the "read input in a signal handler" started that way, too.
- Re: Elisp native profiler, (continued)
- Re: Elisp native profiler, Stefan Monnier, 2012/09/26
- Re: Elisp native profiler, Tomohiro Matsuyama, 2012/09/26
- Re: Elisp native profiler, Tomohiro Matsuyama, 2012/09/26
- Re: Elisp native profiler, Paul Eggert, 2012/09/26
- Re: Elisp native profiler, Ivan Andrus, 2012/09/26
- Re: Elisp native profiler, Paul Eggert, 2012/09/26
- Re: Elisp native profiler,
Eli Zaretskii <=
- Re: Elisp native profiler, Stefan Monnier, 2012/09/25
- Re: Elisp native profiler, Stephen J. Turnbull, 2012/09/25
- Re: Elisp native profiler, Stefan Monnier, 2012/09/25
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/26
- Re: Elisp native profiler, Stefan Monnier, 2012/09/26
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/26
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/26
- Re: Elisp native profiler, Stefan Monnier, 2012/09/26
- Re: Elisp native profiler, Eli Zaretskii, 2012/09/26
- Re: Elisp native profiler, Stefan Monnier, 2012/09/26