Tiny C Compiler
||This article has an unclear citation style. (July 2012)|
|Stable release||0.9.26 / February 15, 2013|
|Written in||C and Assembly|
|Operating system||Linux, Unix, Windows|
|License||GNU Lesser General Public License|
The Tiny C Compiler (aka TCC, tCc, or TinyCC) is an x86, x86-64 and ARM processor C compiler created by Fabrice Bellard. It is designed to work for slow computers with little disk space (e.g. on rescue disks). Windows operating system support was added in version 0.9.23 (17 Jun 2005). TCC is distributed under the GNU Lesser General Public License (LGPL).
TCC has a number of features which differentiate it from other current C compilers:
- Its small file size (about 100 KB for the x86 TCC executable) and memory footprint allow it to be used directly from a single 1.44 M floppy disk, such as a rescue disk.
- TCC is intended to produce native x86, x86-64 and ARM code very quickly; according to Bellard, it compiles, assembles and links about nine times faster than GCC does.
- TCC has a number of compiler-specific language features intended to improve its practicality, such as an optional memory and bound checker, for improved code stability.
- TCC allows programs to be run automatically at compile time using a command-line switch. This allows programs to be run as a shell script under Unix-like systems which support the shebang interpreter directive syntax.
Compiled program performance
Although the TCC compiler itself is exceptionally fast, there is an inherent trade off between this size of the compiler and the performance of the code which TCC produces.
TCC does perform a few optimizations, such as constant propagation for all operations, multiplications and divisions are optimized to shifts when appropriate, and comparison operators are specially optimized (by maintaining a special cache for the processor flags). It also does some simple register allocation, which prevents many extraneous save/load pairs inside a single statement.
But in general, TCC's implementation emphasizes smallness instead of optimally-performing results. TCC generates code in a single pass, and does not perform most of the optimizations performed by other compilers such as GCC. TCC compiles every statement on its own, and at the end of each statement register values are written back to the stack and must be re-read even if the next line uses the values in registers (creating extraneous save/load pairs between statements). TCC uses only some of the available registers (e.g., on x86 it never uses ebx, esi, or edi because they need to be preserved across function calls).
Here are two benchmark examples:
- Rough benchmarks of a recursive Fibonacci algorithm on a 1.8 GHz Intel Centrino laptop with 512 MB RAM yields a noticeable difference in results between Microsoft Visual C++ compiler 13.10.3052 and TCC. To calculate the 49th Fibonacci number, it took a TCC-compiled program approximately 18% longer than the MS Visual C++ compiled program.
- With a tcc modified to compile GCC, running cc1 (the GCC C compiler) on itself required 518 seconds when compiled using GCC 3.4.2, 558 seconds using GCC 2.95.3, 545 using Microsoft C compiler, and 1145 seconds using tcc. The level of optimization in each compiler was -O1 or similar.
Well-known uses of tcc include:
- TCCBOOT, a hack where TCC loads and boots a Linux kernel from source in about 10 seconds. That is to say, it is a "boot loader" which reads Linux kernel source code from disk, writes executable instructions to memory, and begins running it. This did require changes to the Linux build process.
- TCC was used to demonstrate a defense against the trust attack.
- TCC has been used to compile GCC, though various patches were required to make this work.
- Cinpy is a Python library that allows you to implement functions with C in Python modules. The functions are compiled with TCC at runtime. The results are made callable in Python through the ctypes library.
TCC has its origins in the Obfuscated Tiny C Compiler (OTCC), a program Bellard wrote to win the International Obfuscated C Code Contest (IOCCC) in 2001. Since that time, Bellard expanded and un-obfuscated the program to produce tcc.
Rob Landley created a fork of tcc that incorporated various patches from others, using the Mercurial SCM; Landley's Mercurial branch showed its current status while the project was active. The project was discontinued on October 4, 2007 and recontinued as a fork on October 27, 2007  then discontinued again on September 5, 2008. Since then, TCC has received two updates; one on 20 May 2009, and 15 Feb 2013.
Various others have distributed patches or download sites of various improved versions of tcc, such as Dave Dodge's collection of unofficial tcc patches, Debian and kfreebsd downstream patches, and grischka's gcc patches. grischka's Public Git Hosting  contains a mob branch with recent contributions, including a shared build, cross-compilers, and SELinux compatibility.
- Tiny C Compiler Reference Documentation accessed on 2008-08-07
- According to the project's TODO list complex types are the only missing C99 feature. Variable Length Arrays have been added in TCC 0.9.26
- Tiny C Compiler homepage
- Glöckner, Daniel. Re: Tinycc-devel (no subject), September 8, 2006.
- grischka, GCC by TCC (some fixes), 29 Sep 2005
- Wheeler, David A. Countering Trusting Trust through Diverse Double-Compiling. ACSAC.
- tinycc-devel (thread)
- Bellard, Fabrice. Obfuscated Tiny C Compiler
- Rob Landley's TCC fork that went inactive
- Landley's Mercurial branch
- tinycc-devel (message)
- Dave Dodge's collection of unofficial tcc patches
- Debian and kfreebsd downstream patches
- grischka, Public Git Hosting for tcc
- grischka, mob branch for tcc