# HG changeset patch # User Rob Landley # Date 1193794914 18000 # Node ID 66af5fe9fc2b07b65c6c155dbfea2477d1ec67c0 # Parent 28de8a30e841dc34aae1d99be23bc84e32c8289d Replace instances of "tcc" with "tinycc" in documentation. diff -r 28de8a30e841 -r 66af5fe9fc2b www/tinycc-doc.html --- a/www/tinycc-doc.html Tue Oct 30 20:35:15 2007 -0500 +++ b/www/tinycc-doc.html Tue Oct 30 20:41:54 2007 -0500 @@ -38,7 +38,7 @@

7. The libtinycc library

8. Developer's guide

8.1 File reading @@ -64,42 +64,42 @@

1. Introduction

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

-TCC compiles so fast that even for big projects Makefiles may +Tinycc compiles so fast that even for big projects Makefiles may not be necessary. -

TCC not only supports ANSI C, but also most of the +

Tinycc not only supports ANSI C, but also most of the ISO C99 standard, and many GNUC extensions including inline assembly.

-TCC can also be used to make C scripts, i.e. pieces of C source +Tinycc can also be used to make C scripts, i.e. pieces of C source that you run as a Perl or Python script. Compilation is so fast that your script will be as fast as if it was an executable.

-TCC can also automatically generate memory and bound checks -(see section 6. TinyCC Memory and Bound checks) while allowing all C pointers operations. TCC can do +Tinycc can also automatically generate memory and bound checks +(see section 6. Tinycc Memory and Bound checks) while allowing all C pointers operations. Tinycc can do these checks even if non patched libraries are used.

-With libtcc, you can use TCC as a backend for dynamic code -generation (see section 7. The libtcc library). +With libtinycc, you can use tinycc as a backend for dynamic code +generation (see section 7. The libtinycc library).

-TCC mainly supports the i386 target on Linux and Windows. There are alpha -ports for the ARM (arm-tcc) and the TMS320C67xx targets -(c67-tcc). More information about the ARM port is available at +Tinycc mainly supports the i386 target on Linux and Windows. There are alpha +ports for the ARM (arm-tinycc) and the TMS320C67xx targets +(c67-tinycc). More information about the ARM port is available at http://lists.gnu.org/archive/html/tinycc-devel/2003-10/msg00044.html. @@ -117,11 +117,11 @@

-usage: tcc [options] [infile1 infile2...] [`-run' infile args...]
+usage: tinycc [options] [infile1 infile2...] [`-run' infile args...]

-TCC options are a very much like gcc options. The main difference is that TCC +Tinycc options are a very much like gcc options. The main difference is that tinycc can also execute directly the resulting program and give it runtime arguments. @@ -132,45 +132,45 @@

`tcc -run a.c' +

`tinycc -run a.c'

Compile `a.c' and execute it directly -

`tcc -run a.c arg1' +

`tinycc -run a.c arg1'

Compile a.c and execute it directly. arg1 is given as first argument to the main() of a.c. -

`tcc a.c -run b.c arg1' +

`tinycc a.c -run b.c arg1'

Compile `a.c' and `b.c', link them together and execute them. arg1 is given as first argument to the main() of the resulting program. Because multiple C files are specified, `--' are necessary to clearly separate the -program arguments from the TCC options. +program arguments from the tinycc options. -

`tcc -o myprog a.c b.c' +

`tinycc -o myprog a.c b.c'

Compile `a.c' and `b.c', link them and generate the executable `myprog'. -

`tcc -o myprog a.o b.o' +

`tinycc -o myprog a.o b.o'

link `a.o' and `b.o' together and generate the executable `myprog'. -

`tcc -c a.c' +

`tinycc -c a.c'

Compile `a.c' and generate object file `a.o'. -

`tcc -c asmfile.S' +

`tinycc -c asmfile.S'

Preprocess with C preprocess and assemble `asmfile.S' and generate object file `asmfile.o'. -

`tcc -c asmfile.s' +

`tinycc -c asmfile.s'

Assemble (but not preprocess) `asmfile.s' and generate object file `asmfile.o'. -

`tcc -r -o ab.o a.c b.c' +

`tinycc -r -o ab.o a.c b.c'

Compile `a.c' and `b.c', link them together and generate the object file `ab.o'. @@ -181,13 +181,13 @@

-TCC can be invoked from scripts, just as shell scripts. You just -need to add #!/usr/local/bin/tcc -run at the start of your C source: +Tinycc can be invoked from scripts, just as shell scripts. You just +need to add #!/usr/local/bin/tinycc -run at the start of your C source:

-#!/usr/local/bin/tcc -run
+#!/usr/local/bin/tinycc -run
 #include <stdio.h>
 
 int main() 
@@ -209,7 +209,7 @@
 
 `-v'
 

-Display current TCC version.
+Display current tinycc version.
 
 
`-c'
 

@@ -221,8 +221,8 @@
 
 
`-Bdir'
 

-Set the path where the tcc internal libraries can be found (default is
-`PREFIX/lib/tcc').
+Set the path where the tinycc internal libraries can be found (default is
+`PREFIX/lib/tinycc').
 
 
`-bench'
 

@@ -232,19 +232,19 @@
 

 Compile file source and run it with the command line arguments
 args. In order to be able to give more than one argument to a
-script, several TCC options can be given after the
+script, several tinycc options can be given after the
 `-run' option, separated by spaces. Example:
 
 
 -tcc "-run -L/usr/X11R6/lib -lX11" ex4.c
+tinycc "-run -L/usr/X11R6/lib -lX11" ex4.c
 
 
 In a script, it gives the following header:
 
 
 -#!/usr/local/bin/tcc -run -L/usr/X11R6/lib -lX11
+#!/usr/local/bin/tinycc -run -L/usr/X11R6/lib -lX11
 #include <stdlib.h>
 int main(int argc, char **argv)
 {
@@ -267,7 +267,7 @@
 
 System include paths are always searched after. The default system
 include paths are: `/usr/local/include', `/usr/include'
-and `PREFIX/lib/tcc/include'. (`PREFIX' is usually
+and `PREFIX/lib/tinycc/include'. (`PREFIX' is usually
 `/usr' or `/usr/local').
 
 `-Dsym[=val]'
@@ -335,7 +335,7 @@
 
 
`-Wunsupported'
 

-Warn about unsupported GCC features that are ignored by TCC.
+Warn about unsupported GCC features that are ignored by tinycc.
 
 
`-Wwrite-strings'
 

@@ -452,7 +452,7 @@
 3.1 ANSI C
 
 
-TCC implements all the ANSI C standard, including structure bit fields
+Tinycc implements all the ANSI C standard, including structure bit fields
 and floating point numbers (long double, double, and
 float fully supported).
 
@@ -461,7 +461,7 @@
 
 
3.2 ISOC99 extensions
 
-TCC implements many features of the
+
Tinycc implements many features of the
 ISO C99
 standard. Currently missing items are: complex and imaginary numbers and
 variable length arrays.
@@ -548,7 +548,7 @@
 
 
 
-TCC implements some GNU C extensions:
+Tinycc implements some GNU C extensions:
 
 
 
@@ -695,7 +695,7 @@
 
 
 
-TCC includes its own x86 inline assembler with a gas-like (GNU
+Tinycc includes its own x86 inline assembler with a gas-like (GNU
 assembler) syntax. No intermediate files are generated. GCC 3.x named
 operands are supported.
 
@@ -716,7 +716,7 @@
 
 __TINYC__ is a predefined macro to 1 to
 
-indicate that you use TCC.
+indicate that you use tinycc.
 
 
#! at the start of a line is ignored to allow scripting.
 
@@ -932,7 +932,7 @@
 
 
 
-TCC can directly output relocatable ELF files (object files),
+Tinycc can directly output relocatable ELF files (object files),
 executable ELF files and dynamic ELF libraries without relying on an
 external linker.
 
@@ -940,11 +940,11 @@
 

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

-TCC linker eliminates unreferenced object code in libraries. A single pass is
+Tinycc linker eliminates unreferenced object code in libraries. A single pass is
 done on the object and library list, so the order in which object files and
 libraries are specified is important (same constraint as GNU ld). No grouping
 options (`--start-group' and `--end-group') are supported.
@@ -955,7 +955,7 @@
 
5.2 ELF file loader
 
 
-TCC can load ELF object files, archives (.a files) and dynamic
+Tinycc can load ELF object files, archives (.a files) and dynamic
 libraries (.so).
 
 
@@ -967,13 +967,13 @@
 
 
 

-TCC for Windows supports the native Win32 executable file format (PE-i386). It
+Tinycc for Windows supports the native Win32 executable file format (PE-i386). It
 generates both EXE and DLL files. DLL symbols can be imported thru DEF files
 generated with the tiny_impdef tool.
 
 
 

-Currently TCC for Windows cannot generate nor read PE object files, so ELF
+Currently tinycc for Windows cannot generate nor read PE object files, so ELF
 object files are used for that purpose. It can be a problem if
 interoperability with MSVC is needed. Moreover, no leading underscore is
 currently generated in the ELF symbols.
@@ -994,7 +994,7 @@
 

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

@@ -1108,21 +1108,21 @@
 
 
 
-
7. The libtcc library
+7. The libtinycc library
 
 
-The libtcc library enables you to use TCC as a backend for
+The libtinycc library enables you to use tinycc as a backend for
 dynamic code generation. 
 
 
 

-Read the `libtcc.h' to have an overview of the API. Read
-`libtcc_test.c' to have a very simple example.
+Read the `libtinycc.h' to have an overview of the API. Read
+`libtinycc_test.c' to have a very simple example.
 
 
 

 The idea consists in giving a C string containing the program you want
-to compile directly to libtcc. Then you can access to any global
+to compile directly to libtinycc. Then you can access to any global
 symbol (function or variable) defined.
 
 
@@ -1131,8 +1131,8 @@
 
8. Developer's guide
 
 
-This chapter gives some hints to understand how TCC works. You can skip
-it if you do not intend to modify the TCC code.
+This chapter gives some hints to understand how tinycc works. You can skip
+it if you do not intend to modify the tinycc code.
 
 
 
@@ -1141,8 +1141,8 @@
 
 

 The BufferedFile structure contains the context needed to read a
-file, including the current line number. tcc_open() opens a new
-file and tcc_close() closes it. inp() returns the next
+file, including the current line number. tinycc_open() opens a new
+file and tinycc_close() closes it. inp() returns the next
 character.
 
 
@@ -1191,7 +1191,7 @@
 
 

 The types are stored in a single 'int' variable. It was choosen in the
-first stages of development when tcc was much simpler. Now, it may not
+first stages of development when tinycc was much simpler. Now, it may not
 be the best solution.
 
 
@@ -1384,14 +1384,14 @@
 
8.7.1 Introduction
 
 
-The TCC code generator directly generates linked binary code in one
+The tinycc 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 can be very fast and surprisingly
 little complicated.
 
 
 

-The TCC code generator is register based. Optimization is only done at
+The tinycc 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 value stack.
 
@@ -1482,7 +1482,7 @@
 the wanted value. 
 
 Understanding the use VT_LVAL is very important if you want to
-understand how TCC works.
+understand how tinycc works.
 
 
VT_LVAL_BYTE

1. Introduction

3.1 ANSI C

3.2 ISOC99 extensions

5.2 ELF file loader

7. The `libtcc` library

7. The `libtinycc` library

8. Developer's guide

8.7.1 Introduction