From 365fc14aa4c5033422481d9145cba015821df052 Mon Sep 17 00:00:00 2001 From: Stefan Monnier Date: Wed, 21 Nov 2012 09:14:42 -0500 Subject: [PATCH] * doc/lispref/debugging.texi (Profiling): Make it more clear that --enable-profiling is about profiling the C code. --- doc/lispref/ChangeLog | 5 +++++ doc/lispref/debugging.texi | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index b5bbd8ef93f..40bd3c2cbbe 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,3 +1,8 @@ +2012-11-21 Stefan Monnier + + * debugging.texi (Profiling): Make it more clear + that --enable-profiling is about profiling the C code. + 2012-11-21 Glenn Morris * debugging.texi (Profiling): Mention --enable-profiling (if !tex). diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi index 3439a8ae152..6e4f6628637 100644 --- 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 -- 2.39.2