From 5ebb1ee6c92a14649d480db44a0c1a8b901369e4 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Tue, 18 Jun 2013 10:15:25 -0700 Subject: [PATCH] Spelling fixes. --- etc/DEBUG | 2 +- src/lisp.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/etc/DEBUG b/etc/DEBUG index 61a8ee05e27..b2a943f5d71 100644 --- a/etc/DEBUG +++ b/etc/DEBUG @@ -26,7 +26,7 @@ described in the node "Auto-loading safe path" in the GDB user manual. ** 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 diff --git a/src/lisp.h b/src/lisp.h index e4033a2f45b..3a4819c763e 100644 --- a/src/lisp.h +++ b/src/lisp.h @@ -226,7 +226,7 @@ enum enum_USE_LSB_TAG { USE_LSB_TAG = 0 }; 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) -- 2.39.2