Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
365fc14a
Commit
365fc14a
authored
Nov 21, 2012
by
Stefan Monnier
Browse files
* doc/lispref/debugging.texi (Profiling): Make it more clear
that --enable-profiling is about profiling the C code.
parent
0e69443d
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
6 additions
and
1 deletion
+6
-1
doc/lispref/ChangeLog
doc/lispref/ChangeLog
+5
-0
doc/lispref/debugging.texi
doc/lispref/debugging.texi
+1
-1
No files found.
doc/lispref/ChangeLog
View file @
365fc14a
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).
...
...
doc/lispref/debugging.texi
View file @
365fc14a
...
...
@@ -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
profil
ing of
Emacs
itself
, you can build it using the
To
profil
e
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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment