* doc/lispref/debugging.texi (Profiling): Make it more clear

that --enable-profiling is about profiling the C code.

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index b5bbd8ef93f7a3964da73c083ed16206db2dcc14..40bd3c2cbbede1a78ac6312c8cb62e19e01751a0 100644 (file)
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -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).

diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index 3439a8ae152f9adc8857557fb52d044bd9df8f0b..6e4f66286377210048fb9c33e77f6411a0514859 100644 (file)
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -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