[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] trunk r113051: Spelling fixes.
From: |
Paul Eggert |
Subject: |
[Emacs-diffs] trunk r113051: Spelling fixes. |
Date: |
Tue, 18 Jun 2013 17:15:29 +0000 |
User-agent: |
Bazaar (2.6b2) |
------------------------------------------------------------
revno: 113051
revision-id: address@hidden
parent: address@hidden
committer: Paul Eggert <address@hidden>
branch nick: trunk
timestamp: Tue 2013-06-18 10:15:25 -0700
message:
Spelling fixes.
modified:
etc/DEBUG debug-20091113204419-o5vbwnq5f7feedwu-1486
src/lisp.h lisp.h-20091113204419-o5vbwnq5f7feedwu-253
=== modified file 'etc/DEBUG'
--- a/etc/DEBUG 2013-06-13 17:52:21 +0000
+++ b/etc/DEBUG 2013-06-18 17:15:25 +0000
@@ -26,7 +26,7 @@
** When you are trying to analyze failed assertions or backtraces, it
is essential to compile Emacs with flags suitable for debugging.
With GCC 4.8 or later, you can invoke 'make' with CFLAGS="-Og -g3".
-With older GCC or non-GCC commpilers, you can use CFLAGS="-O0 -g3".
+With older GCC or non-GCC compilers, you can use CFLAGS="-O0 -g3".
With GCC and higher optimization levels such as -O2, the
-fno-omit-frame-pointer and -fno-crossjumping options are often
essential. The latter prevents GCC from using the same abort call for
=== modified file 'src/lisp.h'
--- a/src/lisp.h 2013-06-18 07:42:37 +0000
+++ b/src/lisp.h 2013-06-18 17:15:25 +0000
@@ -226,7 +226,7 @@
would otherwise cause a serious performance problem.
For each such operation OP, define a macro lisp_h_OP that contains
- the operation's implementation. That way, OP can be implementated
+ the operation's implementation. That way, OP can be implemented
via a macro definition like this:
#define OP(x) lisp_h_OP (x)
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] trunk r113051: Spelling fixes.,
Paul Eggert <=