[Tinycc-devel] [PATCH] [2/2] tcc-doc.texi

[Peter \"Firefly\" Lund]

Spelling fixes, typos.

 tcc-doc.texi |   48 ++++++++++++++++++++++++------------------------
 1 files changed, 24 insertions(+), 24 deletions(-)

-Peter

"Compared to a modern architecture like the Alpha, the
JavaCPU looks like something an undergrad dreamed up in the men's room
based on the mathematical elegance of two urinal cakes, one stacked
upon the other."

--- tcc-3/tcc-doc.texi  Thu Mar  6 01:01:12 2003
+++ tcc-3b/tcc-doc.texi Thu Mar  6 01:56:54 2003
@@ -42,7 +42,7 @@
 @chapter Introduction

 TinyCC (aka TCC) is a small but hyper fast C compiler. Unlike other C
-compilers, it is meant to be self-suffisant: you do not need an
+compilers, it is meant to be self-relying: you do not need an
 external assembler or linker because TCC does that for you.

 TCC compiles so @emph{fast} that even for big projects @code{Makefile}s may
@@ -155,7 +155,7 @@

 @table @option
 @item -Idir
-Specify an additionnal include path. Include paths are searched in the
+Specify an additional include path. Include paths are searched in the
 order they are specified.

 System include paths are always searched after. The default system
@@ -176,7 +176,7 @@

 @table @option
 @item -Ldir
-Specify an additionnal static library path for the @option{-l} option. The
+Specify an additional static library path for the @option{-l} option. The
 default library paths are @file{/usr/local/lib}, @file{/usr/lib} and 
@file{/lib}.

 @item -lxxx
@@ -208,7 +208,7 @@
 fault}.

 @item -b
-Generate additionnal support code to check
+Generate additional support code to check
 memory allocations and array/pointer bounds. @option{-g} is implied. Note
 that the generated code is slower and bigger in this case.

@@ -541,12 +541,12 @@
 external linker.

 Dynamic ELF libraries can be output but the C compiler does not generate
-position independant code (PIC) code. It means that the dynamic librairy
+position independent code (PIC). It means that the dynamic librairy
 code generated by TCC cannot be factorized among processes yet.

-TCC linker cannot currently suppress unused object code. But TCC
+TCC linker cannot currently eliminate unused object code. But TCC
 will soon integrate a novel feature not found in GNU tools: unused code
-will be suppressed at the function or variable level, provided you only
+will be eliminated at the function or variable level, provided you only
 use TCC to compile your files.

 @section ELF file loader
@@ -562,7 +562,7 @@

 Because on many Linux systems some dynamic libraries (such as
 @file{/usr/lib/libc.so}) are in fact GNU ld link scripts (horrible!),
-TCC linker also support a subset of GNU ld scripts.
+the TCC linker also supports a subset of GNU ld scripts.

 The @code{GROUP} and @code{FILE} commands are supported.

@@ -586,10 +586,10 @@
 code. When a pointer comes from unchecked code, it is assumed to be
 valid. Even very obscure C code with casts should work correctly.

-To have more information about the ideas behind this method, check at
+For more information about the ideas behind this method, see
 @url{http://www.doc.ic.ac.uk/~phjk/BoundsChecking.html}.

-Here are some examples of catched errors:
+Here are some examples of caught errors:

 @table @asis

@@ -601,7 +601,7 @@
 @}
 @end example

address@hidden Bound error in global or local arrays:
address@hidden Out of bounds-error in global or local arrays:
 @example
 @{
     int tab[10];
@@ -611,7 +611,7 @@
 @}
 @end example

address@hidden Bound error in allocated data:
address@hidden Out of bounds-error in malloc'ed data:
 @example
 @{
     int *tab;
@@ -623,7 +623,7 @@
 @}
 @end example

address@hidden Access to a freed region:
address@hidden Access of freed memory:
 @example
 @{
     int *tab;
@@ -635,7 +635,7 @@
 @}
 @end example

address@hidden Freeing an already freed region:
address@hidden Double free:
 @example
 @{
     int *tab;
@@ -680,7 +680,7 @@

 @code{tok} contains the current token (see @code{TOK_xxx})
 constants. Identifiers and keywords are also keywords. @code{tokc}
-contains additionnal infos about the token (for example a constant value
+contains additional infos about the token (for example a constant value
 if number or string token).

 @section Parser
@@ -837,15 +837,15 @@

 The TCC code generator directly generates linked binary code in one
 pass. It is rather unusual these days (see gcc for example which
-generates text assembly), but it allows to be very fast and surprisingly
-not so complicated.
+generates text assembly), but it can be very fast and surprisingly
+little complicated.

 The TCC code generator is register based. Optimization is only done at
 the expression level. No intermediate representation of expression is
 kept except the current values stored in the @emph{value stack}.

 On x86, three temporary registers are used. When more registers are
-needed, one register is flushed in a new local variable.
+needed, one register is spilled into a new temporary variable on the stack.

 @subsection The value stack
 @cindex value stack, introduction
@@ -856,7 +856,7 @@

 @code{SValue.t} is the type. @code{SValue.r} indicates how the value is
 currently stored in the generated code. It is usually a CPU register
-index (@code{REG_xxx} constants), but additionnal values and flags are
+index (@code{REG_xxx} constants), but additional values and flags are
 defined:

 @example
@@ -897,8 +897,8 @@

 @item VT_JMP
 @itemx VT_JMPI
-indicates that the value is the consequence of a jmp. For VT_JMP, it is
-1 if the jump is taken, 0 otherwise. For VT_JMPI it is inverted.
+indicates that the value is the consequence of a conditional jump. For VT_JMP,
+it is 1 if the jump is taken, 0 otherwise. For VT_JMPI it is inverted.

 These values are used to compile the @code{||} and @code{&&} logical
 operators.
@@ -919,10 +919,10 @@
 @itemx VT_LVAL_SHORT
 @itemx VT_LVAL_UNSIGNED
 if the lvalue has an integer type, then these flags give its real
-type. The type alone is not suffisant in case of cast optimisations.
+type. The type alone is not enough in case of cast optimisations.

 @item VT_LLOCAL
-is a saved lvalue on the stack. @code{VT_LLOCAL} should be suppressed
+is a saved lvalue on the stack. @code{VT_LLOCAL} should be eliminated
 ASAP because its semantics are rather complicated.

 @item VT_MUSTCAST
@@ -1002,7 +1002,7 @@

 @item gen_bounded_ptr_add()
 @item gen_bounded_ptr_deref()
-are only used for bound checking.
+are only used for bounds checking.

 @end table