The latest version of Ch and Embedded Ch is 8.0.0. You can check Ch revision history for the detailed new features in Ch 8.0.0. Ch Professional Edition for ARM and Raspberry PI is free for non-commercial use, subject to the license agreement set forth in the license.

1. Tiny C Compiler Windows 7 Free Download
2. Best C++ Compiler Download

Table of Contents

• 2 Command line invocation
• 3 C language support
• 4 TinyCC Assembler
• 5 TinyCC Linker
• 8 Developer’s guide
  • 8.7 Code generation

1. The Tiny C Compiler (a.k.a. TCC, tCc, or TinyCC) is an x86, X86-64 and ARM processor C compiler initially written 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.
2. The C166 C Compiler is the most efficient and flexible C16x development tool set available. It supports all derivatives and is fully compatible with all major emulator vendors. More information about the Keil A166 Macro Assembler may be found in the Getting Started with the C16x User's Guide which provides an introduction to the Keil C166.

This manual documents version 0.9.27 of the Tiny C Compiler.

1 Introduction

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

TCC compiles so fast that even for big projects Makefiles maynot be necessary.

TCC not only supports ANSI C, but also most of the new ISO C99standard and many GNUC extensions including inline assembly.

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

TCC can also automatically generate memory and bound checks(see Bounds) while allowing all C pointers operations. TCC can dothese checks even if non patched libraries are used.

With libtcc, you can use TCC as a backend for dynamic codegeneration (see Libtcc).

TCC mainly supports the i386 target on Linux and Windows. There are alphaports for the ARM (arm-tcc) and the TMS320C67xx targets(c67-tcc). More information about the ARM port is available athttp://lists.gnu.org/archive/html/tinycc-devel/2003-10/msg00044.html.

For usage on Windows, see also tcc-win32.txt.

2 Command line invocation

2.1 Quick start

TCC options are a very much like gcc options. The main difference is that TCCcan also execute directly the resulting program and give it runtimearguments.

Here are some examples to understand the logic:

Compile a.c and execute it directly

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

Compile a.c and b.c, link them together and execute them. arg1 is givenas first argument to the main() of the resulting program.

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

link a.o and b.o together and generate the executable myprog.

Compile a.c and generate object file a.o.

Preprocess with C preprocess and assemble asmfile.S and generateobject file asmfile.o.

Assemble (but not preprocess) asmfile.s and generate object fileasmfile.o.

Compile a.c and b.c, link them together and generate the object file ab.o.

Scripting:

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

TCC can read C source code from standard input when - is used in place of infile. Example:

2.2 Option summary

General Options:

Generate an object file.

Put object file, executable, or dll into output file outfile.

Compile file source and run it with the command line argumentsargs. In order to be able to give more than one argument to ascript, several TCC options can be given after the-run option, separated by spaces:

In a script, it gives the following header:

Display TCC version.

Show included files. As sole argument, print search dirs. -vvv shows tries too.

Display compilation statistics.

Preprocessor options:

Specify an additional include path. Include paths are searched in theorder they are specified.

System include paths are always searched after. The default systeminclude paths are: /usr/local/include, /usr/includeand PREFIX/lib/tcc/include. (PREFIX is usually/usr or /usr/local).

Define preprocessor symbol ‘sym’ toval. If val is not present, its value is ‘1’. Function-like macros canalso be defined: -DF(a)=a+1

Undefine preprocessor symbol ‘sym’.

Preprocess only, to stdout or file (with -o).

Compilation flags:

Note: each of the following options has a negative form beginning with-fno-.

Let the char type be unsigned.

Let the char type be signed.

Do not generate common symbols for uninitialized data.

Add a leading underscore at the beginning of each C symbol.

Allow a MS C compiler extensions to the language. Currently thisassumes a nested named structure declaration without an identifierbehaves like an unnamed one.

Allow dollar signs in identifiers

Warning options:

Disable all warnings.

Note: each of the following warning options has a negative form beginning with-Wno-.

Warn about implicit function declaration.

Warn about unsupported GCC features that are ignored by TCC.

Make string constants be of type const char * instead of char*.

Abort compilation if warnings are issued.

Activate all warnings, except -Werror, -Wunusupported and-Wwrite-strings.

Linker options:

Specify an additional static library path for the -l option. Thedefault library paths are /usr/local/lib, /usr/lib and /lib.

Link your program with dynamic library libxxx.so or static librarylibxxx.a. The library is searched in the paths specified by the-L option and LIBRARY_PATH variable.

Set the path where the tcc internal libraries (and include files) can befound (default is PREFIX/lib/tcc).

Generate a shared library instead of an executable.

set name for shared library to be used at runtime

Generate a statically linked executable (default is a shared linkedexecutable).

Export global symbols to the dynamic linker. It is useful when a libraryopened with dlopen() needs to access executable symbols.

Generate an object file combining all input files.

Put custom search path for dynamic libraries into executable.

When putting a custom search path for dynamic libraries into the executable,create the new ELF dynamic tag DT_RUNPATH instead of the old legacy DT_RPATH.

Use fmt as output format. The supported output formats are:

ELF output format (default)

Binary image (only for executable output)

COFF output format (only for executable output for TMS320C67xx target)

Set type for PE (Windows) executables.

Modify executable layout.

Set DT_SYMBOLIC tag.

Turn on/off linking of all objects in archives.

Debugger options:

Generate run time debug information so that you get clear run timeerror messages: test.c:68: in function 'test5()': dereferencinginvalid pointer instead of the laconic Segmentationfault.

Generate additional support code to checkmemory allocations and array/pointer bounds. -g is implied. Notethat the generated code is slower and bigger in this case.

Note: -b is only available on i386 when using libtcc for the moment.

Display N callers in stack traces. This is useful with -g or-b.

Misc options:

Generate makefile fragment with dependencies.

Use depfile as output for -MD.

Print the configured installation directory and a list of libraryand include directories tcc will search.

Print version.

Target specific options:

Use an algorithm for bitfield alignment consistent with MSVC. Default isgcc’s algorithm.

Select the float ABI. Possible values: softfp and hard

Do not use sse registers on x86_64

Pass command line to the i386/x86_64 cross compiler.

Note: GCC options -Ox, -fx and -mx areignored.

Environment variables that affect how tcc operates.

A colon-separated list of directories searched for include files,directories given with -I are searched first.

A colon-separated list of directories searched for libraries for the-l option, directories given with -L are searched first.

3 C language support

3.1 ANSI C

TCC implements all the ANSI C standard, including structure bit fieldsand floating point numbers (long double, double, andfloat fully supported).

3.2 ISOC99 extensions

TCC implements many features of the new C standard: ISO C99. Currentlymissing items are: complex and imaginary numbers.

Currently implemented ISOC99 features:

• variable length arrays.
• 64 bit long long types are fully supported.
• The boolean type _Bool is supported.
• __func__ is a string variable containing the currentfunction name.
• Variadic macros: __VA_ARGS__ can be used for function-like macros:

  dprintf can then be used with a variable number of parameters.

• Declarations can appear anywhere in a block (as in C++).
• Array and struct/union elements can be initialized in any order by using designators:
• Compound initializers are supported:

  to initialize a pointer pointing to an initialized array. The sameworks for structures and strings.

• Hexadecimal floating point constants are supported:

  is the same as writing

• inline keyword is ignored.
• restrict keyword is ignored.

3.3 GNU C extensions

TCC implements some GNU C extensions:

• array designators can be used without ’=’:
• Structure field designators can be a label:

  instead of

• e is ASCII character 27.
• case ranges : ranges can be used in cases:
• The keyword __attribute__ is handled to specify variable orfunction attributes. The following attributes are supported:
  • aligned(n): align a variable or a structure field to n bytes(must be a power of two).
  • packed: force alignment of a variable or a structure field to 1.
  • section(name): generate function or data in assembly sectionname (name is a string containing the section name) instead of the defaultsection.
  • unused: specify that the variable or the function is unused.
  • cdecl: use standard C calling convention (default).
  • stdcall: use Pascal-like calling convention.
  • regparm(n): use fast i386 calling convention. n must bebetween 1 and 3. The first n function parameters are respectively put inregisters %eax, %edx and %ecx.
  • dllexport: export function from dll/executable (win32 only)

  Here are some examples:

  align variable a to 8 bytes and put it in section .mysection.

  generate function my_add in section .mycodesection.

• GNU style variadic macros:
• __FUNCTION__ is interpreted as C99 __func__ (so it has not exactly the same semantics as string literal GNUCwhere it is a string literal).
• The __alignof__ keyword can be used as sizeof to get the alignment of a type or an expression.
• The typeof(x) returns the type of x. x is an expression or a type.
• Computed gotos: &&label returns a pointer of type void * on the goto label label. goto *expr can beused to jump on the pointer resulting from expr.
• Inline assembly with asm instruction:

  TCC includes its own x86 inline assembler with a gas-like (GNUassembler) syntax. No intermediate files are generated. GCC 3.x namedoperands are supported.

• __builtin_types_compatible_p() and __builtin_constant_p() are supported.
• #pragma pack is supported for win32 compatibility.

3.4 TinyCC extensions

• __TINYC__ is a predefined macro to indicate that you use TCC.
• #! at the start of a line is ignored to allow scripting.
• Binary digits can be entered (0b101 instead of5).
• __BOUNDS_CHECKING_ON is defined if bound checking is activated.

4 TinyCC Assembler

Since version 0.9.16, TinyCC integrates its own assembler. TinyCCassembler supports a gas-like syntax (GNU assembler). You candeactivate assembler support if you want a smaller TinyCC executable(the C compiler does not rely on the assembler).

TinyCC Assembler is used to handle files with .S (Cpreprocessed assembler) and .s extensions. It is also used tohandle the GNU inline assembler with the asm keyword.

4.1 Syntax

TinyCC Assembler supports most of the gas syntax. The tokens are thesame as C.

• C and C++ comments are supported.
• Identifiers are the same as C, so you cannot use ’.’ or ’$’.
• Only 32 bit integer numbers are supported.

4.2 Expressions

• Integers in decimal, octal and hexa are supported.
• Unary operators: +, -, ~.
• Binary operators in decreasing priority order:
  1. *, /, %
  2. &, , ^
  3. +, -
• A value is either an absolute number or a label plus an offset. All operators accept absolute values except ’+’ and ’-’. ’+’ or ’-’ can beused to add an offset to a label. ’-’ supports two labels only if theyare the same or if they are both defined and in the same section.

4.3 Labels

• All labels are considered as local, except undefined ones.
• Numeric labels can be used as local gas-like labels. They can be defined several times in the same source. Use ’b’(backward) or ’f’ (forward) as suffix to reference them:

4.4 Directives

All directives are preceded by a ’.’. The following directives aresupported:

• .align n[,value]
• .skip n[,value]
• .space n[,value]
• .byte value1[,.]
• .word value1[,.]
• .short value1[,.]
• .int value1[,.]
• .long value1[,.]
• .quad immediate_value1[,.]
• .globl symbol
• .global symbol
• .section section
• .text
• .data
• .bss
• .fill repeat[,size[,value]]
• .org n
• .previous
• .string string[,.]
• .asciz string[,.]
• .ascii string[,.]

4.5 X86 Assembler

All X86 opcodes are supported. Only ATT syntax is supported (sourcethen destination operand order). If no size suffix is given, TinyCCtries to guess it from the operand sizes.

Currently, MMX opcodes are supported but not SSE ones.

5 TinyCC Linker

5.1 ELF file generation

TCC can directly output relocatable ELF files (object files),executable ELF files and dynamic ELF libraries without relying on anexternal linker.

Dynamic ELF libraries can be output but the C compiler does not generateposition independent code (PIC). It means that the dynamic librarycode generated by TCC cannot be factorized among processes yet.

TCC linker eliminates unreferenced object code in libraries. A single pass isdone on the object and library list, so the order in which object files andlibraries are specified is important (same constraint as GNU ld). No groupingoptions (--start-group and --end-group) are supported.

5.2 ELF file loader

TCC can load ELF object files, archives (.a files) and dynamiclibraries (.so).

5.3 PE-i386 file generation

TCC for Windows supports the native Win32 executable file format (PE-i386). Itgenerates EXE files (console and gui) and DLL files.

For usage on Windows, see also tcc-win32.txt.

5.4 GNU Linker Scripts

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 GROUP and FILE commands are supported. OUTPUT_FORMATand TARGET are ignored.

Example from /usr/lib/libc.so: Mafia 2 steam keygen free download key generator.

6 TinyCC Memory and Bound checks

This feature is activated with the -b (see Invoke).

Note that pointer size is unchanged and that code generatedwith bound checks is fully compatible with uncheckedcode. When a pointer comes from unchecked code, it is assumed to bevalid. Even very obscure C code with casts should work correctly.

For more information about the ideas behind this method, seehttp://www.doc.ic.ac.uk/~phjk/BoundsChecking.html.

Here are some examples of caught errors:

Invalid range with standard string function:

Out of bounds-error in global or local arrays:

Out of bounds-error in malloc’ed data:

Access of freed memory:

Double free:

7 The libtcc library

The libtcc library enables you to use TCC as a backend fordynamic code generation.

Read the libtcc.h to have an overview of the API. Readlibtcc_test.c to have a very simple example.

The idea consists in giving a C string containing the program you wantto compile directly to libtcc. Then you can access to any globalsymbol (function or variable) defined.

8 Developer’s guide

This chapter gives some hints to understand how TCC works. You can skipit if you do not intend to modify the TCC code.

8.1 File reading

The BufferedFile structure contains the context needed to read afile, including the current line number. tcc_open() opens a newfile and tcc_close() closes it. inp() returns the nextcharacter.

8.2 Lexer

next() reads the next token in the currentfile. next_nomacro() reads the next token without macroexpansion.

tok contains the current token (see TOK_xxx)constants. Identifiers and keywords are also keywords. tokccontains additional infos about the token (for example a constant valueif number or string token).

8.3 Parser

The parser is hardcoded (yacc is not necessary). It does only one pass,except:

• For initialized arrays with unknown size, a first pass is done to count the number of elements.
• For architectures where arguments are evaluated in reverse order, a first pass is done to reverse the argument order.

8.4 Types

The types are stored in a single ’int’ variable. It was chosen in thefirst stages of development when tcc was much simpler. Now, it may notbe the best solution.

When a reference to another type is needed (for pointers, functions andstructures), the 32 - VT_STRUCT_SHIFT high order bits are used tostore an identifier reference.

The VT_UNSIGNED flag can be set for chars, shorts, ints and longlongs.

Arrays are considered as pointers VT_PTR with the flagVT_ARRAY set. Variable length arrays are considered as specialarrays and have flag VT_VLA set instead of VT_ARRAY.

The VT_BITFIELD flag can be set for chars, shorts, ints and longlongs. If it is set, then the bitfield position is stored from bitsVT_STRUCT_SHIFT to VT_STRUCT_SHIFT + 5 and the bit field size is storedfrom bits VT_STRUCT_SHIFT + 6 to VT_STRUCT_SHIFT + 11.

VT_LONG is never used except during parsing.

During parsing, the storage of an object is also stored in the typeinteger:

8.5 Symbols

All symbols are stored in hashed symbol stacks. Each symbol stackcontains Sym structures.

Sym.v contains the symbol name (rememberan identifier is also a token, so a string is never necessary to storeit). Sym.t gives the type of the symbol. Sym.r is usuallythe register in which the corresponding variable is stored. Sym.c isusually a constant associated to the symbol like its address for normalsymbols, and the number of entries for symbols representing arrays.Variable length array types use Sym.c as a location on the stackwhich holds the runtime sizeof for the type.

Four main symbol stacks are defined:

for the macros (#defines).

for the global variables, functions and types.

for the local variables, functions and types.

for the local labels (for goto).

for GCC block local labels (see the __label__ keyword).

sym_push() is used to add a new symbol in the local symbolstack. If no local symbol stack is active, it is added in the globalsymbol stack.

sym_pop(st,b) pops symbols from the symbol stack st untilthe symbol b is on the top of stack. If b is NULL, the stackis emptied.

sym_find(v) return the symbol associated to the identifierv. The local stack is searched first from top to bottom, then theglobal stack.

8.6 Sections

The generated code and data are written in sections. The structureSection contains all the necessary information for a givensection. new_section() creates a new section. ELF file semanticsis assumed for each section.

The following sections are predefined:

is the section containing the generated code. ind contains thecurrent position in the code section.

contains initialized data

contains uninitialized data

are used when bound checking is activated

Tiny C Compiler Windows 7 Free Download

are used when debugging is active to store debug information

contain the exported symbols (currently only used for debugging).

8.7 Code generation

8.7.1 Introduction

The TCC code generator directly generates linked binary code in onepass. It is rather unusual these days (see gcc for example whichgenerates text assembly), but it can be very fast and surprisinglylittle complicated.

The TCC code generator is register based. Optimization is only done atthe expression level. No intermediate representation of expression iskept except the current values stored in the value stack.

On x86, three temporary registers are used. When more registers areneeded, one register is spilled into a new temporary variable on the stack.

8.7.2 The value stack

When an expression is parsed, its value is pushed on the value stack(vstack). The top of the value stack is vtop. Each valuestack entry is the structure SValue.

SValue.t is the type. SValue.r indicates how the value iscurrently stored in the generated code. It is usually a CPU registerindex (REG_xxx constants), but additional values and flags aredefined:

indicates that the value is a constant. It is stored in the unionSValue.c, depending on its type.

indicates a local variable pointer at offset SValue.c.i in thestack.

indicates that the value is actually stored in the CPU flags (i.e. thevalue is the consequence of a test). The value is either 0 or 1. Theactual CPU flags used is indicated in SValue.c.i.

If any code is generated which destroys the CPU flags, this value MUST beput in a normal register.

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.

uconnect keygen These values are used to compile the and && logicaloperators.

If any code is generated, this value MUST be put in a normalregister. Otherwise, the generated code won’t be executed if the jump istaken.

is a flag indicating that the value is actually an lvalue (left value ofan assignment). It means that the value stored is actually a pointer tothe wanted value.

Understanding the use VT_LVAL is very important if you want tounderstand how TCC works.

if the lvalue has an integer type, then these flags give its realtype. The type alone is not enough in case of cast optimisations.

is a saved lvalue on the stack. VT_LVAL must also be set withVT_LLOCAL. VT_LLOCAL can arise when a VT_LVAL ina register has to be saved to the stack, or it can come from anarchitecture-specific calling convention.

Best C++ Compiler Download

indicates that a cast to the value type must be performed if the valueis used (lazy casting).

indicates that the symbol SValue.sym must be added to the constant.

are only used for optional bound checking.

8.7.3 Manipulating the value stack

vsetc() and vset() pushes a new value on the valuestack. If the previous vtop was stored in a very unsafe place(forexample in the CPU flags), then some code is generated to put theprevious vtop in a safe storage.

vpop() pops vtop. In some cases, it also generates cleanupcode (for example if stacked floating point registers are used as onx86).

The gv(rc) function generates code to evaluate vtop (thetop value of the stack) into registers. rc selects in whichregister class the value should be put. gv() is the mostimportant function of the code generator.

gv2() is the same as gv() but for the top two stackentries.

8.7.4 CPU dependent code generation

See the i386-gen.c file to have an example.

must generate the code needed to load a stack value into a register.

must generate the code needed to store a register into a stack valuelvalue.

should generate a function call

should generate a function prolog/epilog.

must generate the binary integer operation op on the two topentries of the stack which are guaranteed to contain integer types.

The result value should be put on the stack.

same as gen_opi() for floating point operations. The two topentries of the stack are guaranteed to contain floating point values ofsame types.

integer to floating point conversion.

floating point to integer conversion.

floating point to floating point of different size conversion.

are only used for bounds checking.

8.8 Optimizations done

Constant propagation is done for all operations. Multiplications anddivisions are optimized to shifts when appropriate. Comparisonoperators are optimized by maintaining a special cache for theprocessor flags. &&, and ! are optimized by maintaining a special’jump target’ value. No other jump optimization is currently performedbecause it would require to store the code in a more abstract fashion.

Concept Index

Tiny C Compiler compiler helps to compile and execute C code