* doc/lispref/debugging.texi (Profiling): Make it more clear
that --enable-profiling is about profiling the C code.
This commit is contained in:
parent
0e69443dde
commit
365fc14aa4
2 changed files with 6 additions and 1 deletions
|
@ -1,3 +1,8 @@
|
|||
2012-11-21 Stefan Monnier <monnier@iro.umontreal.ca>
|
||||
|
||||
* debugging.texi (Profiling): Make it more clear
|
||||
that --enable-profiling is about profiling the C code.
|
||||
|
||||
2012-11-21 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* debugging.texi (Profiling): Mention --enable-profiling (if !tex).
|
||||
|
|
|
@ -866,7 +866,7 @@ You can check the speed of individual Emacs Lisp forms using the
|
|||
@c Not worth putting in the printed manual.
|
||||
@ifnottex
|
||||
@cindex --enable-profiling option of configure
|
||||
For low-level profiling of Emacs itself, you can build it using the
|
||||
To profile Emacs at the level of its C code, you can build it using the
|
||||
@option{--enable-profiling} option of @command{configure}. When Emacs
|
||||
exits, it generates a file @file{gmon.out} that you can examine using
|
||||
the @command{gprof} utility. This feature is mainly useful for
|
||||
|
|
Loading…
Add table
Reference in a new issue