2001-11-12 02:01:29 +08:00
|
|
|
Tiny C Compiler - C Scripting Everywhere - The Smallest ANSI C compiler
|
|
|
|
-----------------------------------------------------------------------
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-11-12 02:01:29 +08:00
|
|
|
Features:
|
|
|
|
--------
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-11-12 02:01:29 +08:00
|
|
|
- SMALL! You can compile and execute C code everywhere, for example on
|
2001-12-03 05:44:40 +08:00
|
|
|
rescue disks (29KB for x86 TCC executable).
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-11-19 00:33:35 +08:00
|
|
|
- FAST! tcc generates optimized x86 code. No byte code
|
|
|
|
overhead. Compiles, assemble and link about 7 times faster than 'gcc
|
|
|
|
-O0'.
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-11-12 02:01:29 +08:00
|
|
|
- UNLIMITED! Any C dynamic library can be used directly. TCC is
|
2001-11-19 00:33:35 +08:00
|
|
|
heading torward full ISOC99 compliance. TCC can of course compile
|
2001-11-12 02:01:29 +08:00
|
|
|
itself.
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-11-12 02:01:29 +08:00
|
|
|
- Compile and execute C source directly. No linking or assembly
|
2001-11-19 00:33:35 +08:00
|
|
|
necessary. Full C preprocessor included.
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-11-12 02:01:29 +08:00
|
|
|
- C script supported : just add '#!/usr/local/bin/tcc' at the first
|
2001-11-12 06:51:50 +08:00
|
|
|
line of your C source, and execute it directly from the command
|
|
|
|
line.
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-11-12 02:01:29 +08:00
|
|
|
Documentation:
|
|
|
|
-------------
|
|
|
|
|
|
|
|
1) Installation
|
|
|
|
|
|
|
|
***TCC currently only work on Linux x86***.
|
|
|
|
|
2001-11-19 00:33:35 +08:00
|
|
|
Type 'make install' to compile and install tcc in /usr/local/bin and
|
2001-11-12 02:01:29 +08:00
|
|
|
/usr/local/lib/tcc.
|
|
|
|
|
|
|
|
2) Introduction
|
|
|
|
|
|
|
|
We assume here that you know ANSI C. Look at the example ex1.c to know
|
|
|
|
what the programs look like.
|
|
|
|
|
2001-11-12 06:51:50 +08:00
|
|
|
The main limitation of tcc is that you cannot use floats.
|
2001-11-12 02:01:29 +08:00
|
|
|
|
|
|
|
The include file <tcclib.h> can be used if you want a small basic libc
|
|
|
|
include support (especially useful for floppy disks). Of course, you
|
|
|
|
can also use standard headers, although they are slower to compile.
|
|
|
|
|
|
|
|
You can begin your C script with '#!/usr/local/bin/tcc' on the first
|
|
|
|
line and set its execute bits (chmod a+x your_script). Then, you can
|
|
|
|
launch the C code as a shell or perl script :-) The command line
|
|
|
|
arguments are put in 'argc' and 'argv' of the main functions, as in
|
|
|
|
ANSI C.
|
|
|
|
|
|
|
|
3) Invokation
|
|
|
|
|
|
|
|
'-Idir' : specify an additionnal include path. The
|
|
|
|
default ones are: /usr/include, /usr/lib/tcc, /usr/local/lib/tcc.
|
|
|
|
|
|
|
|
'-Dsym' : define preprocessor symbol 'sym' to 1.
|
|
|
|
|
|
|
|
'-lxxx' : dynamically link your program with library
|
|
|
|
libxxx.so. Standard library paths are checked, including those
|
|
|
|
specificed with LD_LIBRARY_PATH.
|
|
|
|
|
|
|
|
Only one source code can be compiled. If you have multiple source
|
|
|
|
files, add one which includes all your sources.
|
|
|
|
|
|
|
|
4) Examples
|
|
|
|
|
|
|
|
ex1.c: simplest example (hello world). Can also be launched directly
|
2001-11-19 00:33:35 +08:00
|
|
|
as a script: './ex1.c'.
|
2001-11-12 02:01:29 +08:00
|
|
|
|
|
|
|
ex2.c: more complicated example: find a number with the four
|
|
|
|
operations given a list of numbers (benchmark).
|
|
|
|
|
|
|
|
ex3.c: compute fibonacci numbers (benchmark).
|
|
|
|
|
|
|
|
ex4.c: more complicated: X11 program. Very complicated test in fact
|
2001-11-19 00:33:35 +08:00
|
|
|
because standard headers are being used !
|
2001-11-12 02:01:29 +08:00
|
|
|
|
|
|
|
ex5.c: 'hello world' with standard glibc headers.
|
|
|
|
|
2001-11-19 00:33:35 +08:00
|
|
|
tcc.c: TCC can of course compile itself. Used to check the code
|
|
|
|
generator.
|
2001-11-12 02:01:29 +08:00
|
|
|
|
|
|
|
prog.c: auto test for TCC which tests many subtle possible bugs. Used
|
|
|
|
when doing 'make test'.
|
|
|
|
|
|
|
|
Exact differences with ANSI C:
|
|
|
|
-----------------------------
|
|
|
|
|
2001-12-03 05:44:40 +08:00
|
|
|
- Preprocessor: the preprocessor tokens are the same as C. It means
|
|
|
|
that in some rare cases, preprocessed numbers are not handled
|
|
|
|
exactly as in ANSI C. This approach has the advantage of being
|
|
|
|
simpler and FAST!
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-11-19 00:33:35 +08:00
|
|
|
- Types: floating point numbers are not supported yet.
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-12-03 05:44:40 +08:00
|
|
|
- Bit fields are not supported.
|
2001-11-19 00:33:35 +08:00
|
|
|
|
2001-12-03 05:44:40 +08:00
|
|
|
- Linking: extern variables must appear in a referenced dll and cannot
|
|
|
|
appear in current source.
|
2001-11-19 00:33:35 +08:00
|
|
|
|
|
|
|
Supported ANSI C extensions:
|
|
|
|
---------------------------
|
|
|
|
|
|
|
|
- 'inline' keyword is ignored (ISOC99).
|
|
|
|
|
|
|
|
- 'restrict' keyword is ignored (ISOC99).
|
|
|
|
|
|
|
|
- '__func__' is a string variable containing the current function name (ISOC99).
|
|
|
|
|
2001-12-03 05:44:40 +08:00
|
|
|
- Variadic macros: __VA_ARGS__ can be used for function-like macros (ISOC99):
|
2001-11-19 00:33:35 +08:00
|
|
|
#define dprintf(level, __VA_ARGS__) printf(__VA_ARGS__).
|
|
|
|
|
2001-12-03 05:44:40 +08:00
|
|
|
- Declarations can appear anywhere in a block (ISOC99).
|
|
|
|
|
|
|
|
- Array and struct/union elements can be initialized in any order by
|
|
|
|
using designators (.e.g. { [0].x = 1 }) (ISOC99).
|
|
|
|
|
|
|
|
- Compound initializers are supported (e.g. int *p = (int []){ 1, 2,
|
|
|
|
3}) (ISOC99).
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-12-03 05:44:40 +08:00
|
|
|
- '#!' at the start of a line is ignored to allow scripting.
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-12-03 05:44:40 +08:00
|
|
|
- Binary digits can be entered ('0b101' instead of '5').
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-11-12 06:51:50 +08:00
|
|
|
Technical Description:
|
|
|
|
---------------------
|
|
|
|
|
|
|
|
This is not my first C compiler (see my 'fbcc' compiler) but it
|
|
|
|
contains the first C preprocessor I wrote. The project started as a
|
2001-11-19 00:33:35 +08:00
|
|
|
joke to make the smallest C compiler. Then I expanded it torward
|
|
|
|
ISOC99 compliance. This C compiler is particular because each feature
|
|
|
|
was added while trying to be as simple and compact as possible. For
|
2001-11-12 06:51:50 +08:00
|
|
|
example, no intermediate structure is used to store code or
|
|
|
|
expressions.
|
|
|
|
|
|
|
|
The TCC code generator directly generates linked binary code. 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.
|
|
|
|
|
|
|
|
The TCC code generator is register based. It means that it could even
|
|
|
|
generate good code for RISC processors. On x86, three temporary
|
|
|
|
registers are used. When more registers are needed, one register is
|
|
|
|
flushed in a new local variable.
|
|
|
|
|
|
|
|
Constant propagation is done for all operations. Multiplications and
|
2001-11-19 00:33:35 +08:00
|
|
|
divisions are optimized to shifts when appropriate. Comparison
|
|
|
|
operators are optimized by maintaining a special cache for the
|
|
|
|
processor flags. &&, || and ! are optimized by maintaining a special
|
|
|
|
'jmp target' value. No other jmp optimization is currently performed
|
2001-11-12 06:51:50 +08:00
|
|
|
because it would require to store the code in a more abstract fashion.
|
|
|
|
|
|
|
|
The types and values descriptions are stored in a single 'int'
|
|
|
|
variable (see VT_xxx constants). It was choosen in the first stages of
|
|
|
|
development when tcc was much simpler. Now, it may not be the best
|
|
|
|
solution.
|
|
|
|
|
2001-11-12 02:01:29 +08:00
|
|
|
License:
|
|
|
|
-------
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-11-19 00:33:35 +08:00
|
|
|
TCC is distributed under the GNU General Public License (see COPYING
|
2001-11-12 02:01:29 +08:00
|
|
|
file).
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-11-12 02:01:29 +08:00
|
|
|
I accept only patches where you give your copyright explictely to me
|
|
|
|
to simplify licensing issues.
|
2001-10-28 23:29:01 +08:00
|
|
|
|
2001-11-19 00:33:35 +08:00
|
|
|
Fabrice Bellard - Nov 17, 2001.
|