1 \input texinfo @c -*- texinfo -*-
3 @setfilename tcc-doc.info
4 @settitle Tiny C Compiler Reference Documentation
5 @dircategory Software development
7 * TCC: (tcc-doc). The Tiny C Compiler.
17 @center @titlefont{Tiny C Compiler Reference Documentation}
25 @node Top, Introduction, (dir), (dir)
26 @top Tiny C Compiler Reference Documentation
28 This manual documents version @value{VERSION} of the Tiny C Compiler.
31 * Introduction:: Introduction to tcc.
32 * Invoke:: Invocation of tcc (command line, options).
33 * Clang:: ANSI C and extensions.
34 * asm:: Assembler syntax.
35 * linker:: Output file generation and supported targets.
36 * Bounds:: Automatic bounds-checking of C code.
37 * Libtcc:: The libtcc library.
38 * devel:: Guide for Developers.
45 TinyCC (aka TCC) is a small but hyper fast C compiler. Unlike other C
46 compilers, it is meant to be self-relying: you do not need an
47 external assembler or linker because TCC does that for you.
49 TCC compiles so @emph{fast} that even for big projects @code{Makefile}s may
52 TCC not only supports ANSI C, but also most of the new ISO C99
53 standard and many GNUC extensions including inline assembly.
55 TCC can also be used to make @emph{C scripts}, i.e. pieces of C source
56 that you run as a Perl or Python script. Compilation is so fast that
57 your script will be as fast as if it was an executable.
59 TCC can also automatically generate memory and bound checks
60 (@pxref{Bounds}) while allowing all C pointers operations. TCC can do
61 these checks even if non patched libraries are used.
63 With @code{libtcc}, you can use TCC as a backend for dynamic code
64 generation (@pxref{Libtcc}).
66 TCC mainly supports the i386 target on Linux and Windows. There are alpha
67 ports for the ARM (@code{arm-tcc}) and the TMS320C67xx targets
68 (@code{c67-tcc}). More information about the ARM port is available at
69 @url{http://lists.gnu.org/archive/html/tinycc-devel/2003-10/msg00044.html}.
71 For usage on Windows, see also @url{tcc-win32.txt}.
74 @chapter Command line invocation
80 usage: tcc [options] [@var{infile1} @var{infile2}@dots{}] [@option{-run} @var{infile} @var{args}@dots{}]
85 @c man begin DESCRIPTION
86 TCC options are a very much like gcc options. The main difference is that TCC
87 can also execute directly the resulting program and give it runtime
90 Here are some examples to understand the logic:
93 @item @samp{tcc -run a.c}
94 Compile @file{a.c} and execute it directly
96 @item @samp{tcc -run a.c arg1}
97 Compile a.c and execute it directly. arg1 is given as first argument to
98 the @code{main()} of a.c.
100 @item @samp{tcc a.c -run b.c arg1}
101 Compile @file{a.c} and @file{b.c}, link them together and execute them. arg1 is given
102 as first argument to the @code{main()} of the resulting program.
104 Because multiple C files are specified, @option{--} are necessary to clearly
105 separate the program arguments from the TCC options.
108 @item @samp{tcc -o myprog a.c b.c}
109 Compile @file{a.c} and @file{b.c}, link them and generate the executable @file{myprog}.
111 @item @samp{tcc -o myprog a.o b.o}
112 link @file{a.o} and @file{b.o} together and generate the executable @file{myprog}.
114 @item @samp{tcc -c a.c}
115 Compile @file{a.c} and generate object file @file{a.o}.
117 @item @samp{tcc -c asmfile.S}
118 Preprocess with C preprocess and assemble @file{asmfile.S} and generate
119 object file @file{asmfile.o}.
121 @item @samp{tcc -c asmfile.s}
122 Assemble (but not preprocess) @file{asmfile.s} and generate object file
125 @item @samp{tcc -r -o ab.o a.c b.c}
126 Compile @file{a.c} and @file{b.c}, link them together and generate the object file @file{ab.o}.
132 TCC can be invoked from @emph{scripts}, just as shell scripts. You just
133 need to add @code{#!/usr/local/bin/tcc -run} at the start of your C source:
136 #!/usr/local/bin/tcc -run
141 printf("Hello World\n");
146 TCC can read C source code from @emph{standard input} when @option{-} is used in
147 place of @option{infile}. Example:
150 echo 'main()@{puts("hello");@}' | tcc -run -
154 @section Option summary
161 Generate an object file.
164 Put object file, executable, or dll into output file @file{outfile}.
166 @item -run source [args...]
167 Compile file @var{source} and run it with the command line arguments
168 @var{args}. In order to be able to give more than one argument to a
169 script, several TCC options can be given @emph{after} the
170 @option{-run} option, separated by spaces:
172 tcc "-run -L/usr/X11R6/lib -lX11" ex4.c
174 In a script, it gives the following header:
176 #!/usr/local/bin/tcc -run -L/usr/X11R6/lib -lX11
183 Show included files. As sole argument, print search dirs. -vvv shows tries too.
186 Display compilation statistics.
190 Preprocessor options:
194 Specify an additional include path. Include paths are searched in the
195 order they are specified.
197 System include paths are always searched after. The default system
198 include paths are: @file{/usr/local/include}, @file{/usr/include}
199 and @file{PREFIX/lib/tcc/include}. (@file{PREFIX} is usually
200 @file{/usr} or @file{/usr/local}).
203 Define preprocessor symbol @samp{sym} to
204 val. If val is not present, its value is @samp{1}. Function-like macros can
205 also be defined: @option{-DF(a)=a+1}
208 Undefine preprocessor symbol @samp{sym}.
211 Preprocess only, to stdout or file (with -o).
217 Note: each of the following options has a negative form beginning with
221 @item -funsigned-char
222 Let the @code{char} type be unsigned.
225 Let the @code{char} type be signed.
228 Do not generate common symbols for uninitialized data.
230 @item -fleading-underscore
231 Add a leading underscore at the beginning of each C symbol.
233 @item -fms-extensions
234 Allow a MS C compiler extensions to the language. Currently this
235 assumes a nested named structure declaration without an identifier
236 behaves like an unnamed one.
238 @item -fdollars-in-identifiers
239 Allow dollar signs in identifiers
247 Disable all warnings.
251 Note: each of the following warning options has a negative form beginning with
255 @item -Wimplicit-function-declaration
256 Warn about implicit function declaration.
259 Warn about unsupported GCC features that are ignored by TCC.
261 @item -Wwrite-strings
262 Make string constants be of type @code{const char *} instead of @code{char
266 Abort compilation if warnings are issued.
269 Activate all warnings, except @option{-Werror}, @option{-Wunusupported} and
270 @option{-Wwrite-strings}.
278 Specify an additional static library path for the @option{-l} option. The
279 default library paths are @file{/usr/local/lib}, @file{/usr/lib} and @file{/lib}.
282 Link your program with dynamic library libxxx.so or static library
283 libxxx.a. The library is searched in the paths specified by the
284 @option{-L} option and @env{LIBRARY_PATH} variable.
287 Set the path where the tcc internal libraries (and include files) can be
288 found (default is @file{PREFIX/lib/tcc}).
291 Generate a shared library instead of an executable.
294 set name for shared library to be used at runtime
297 Generate a statically linked executable (default is a shared linked
301 Export global symbols to the dynamic linker. It is useful when a library
302 opened with @code{dlopen()} needs to access executable symbols.
305 Generate an object file combining all input files.
307 @item -Wl,-rpath=path
308 Put custom search path for dynamic libraries into executable.
310 @item -Wl,--enable-new-dtags
311 When putting a custom search path for dynamic libraries into the executable,
312 create the new ELF dynamic tag DT_RUNPATH instead of the old legacy DT_RPATH.
314 @item -Wl,--oformat=fmt
315 Use @var{fmt} as output format. The supported output formats are:
318 ELF output format (default)
320 Binary image (only for executable output)
322 COFF output format (only for executable output for TMS320C67xx target)
325 @item -Wl,--export-all-symbols
326 @item -Wl,--export-dynamic
327 Export global symbols to the dynamic linker. It is useful when a library
328 opened with @code{dlopen()} needs to access executable symbols.
330 @item -Wl,-subsystem=console/gui/wince/...
331 Set type for PE (Windows) executables.
333 @item -Wl,-[Ttext=# | section-alignment=# | file-alignment=# | image-base=# | stack=#]
334 Modify executable layout.
339 @item -Wl,-(no-)whole-archive
340 Turn on/off linking of all objects in archives.
348 Generate run time debug information so that you get clear run time
349 error messages: @code{ test.c:68: in function 'test5()': dereferencing
350 invalid pointer} instead of the laconic @code{Segmentation
354 Generate additional support code to check
355 memory allocations and array/pointer bounds. @option{-g} is implied. Note
356 that the generated code is slower and bigger in this case.
357 The bound checking code is not included in shared libaries. The main executable should always be compiled with the @option{-b}.
359 There are three environment variables that can be used:
361 @item TCC_BOUNDS_PRINT_CALLS
362 Print bound checking calls. Can be used for debugging.
363 @item TCC_BOUNDS_PRINT_HEAP
364 Print heap objects that are not freed at exit of program.
365 @item TCC_BOUNDS_NEVER_FATAL
366 Try to continue in case of a bound checking error.
369 Note: @option{-b} is only available on i386 (linux and windows) and x86_64 (linux and windows) when using libtcc for the moment.
372 Display N callers in stack traces. This is useful with @option{-g} or
381 Generate makefile fragment with dependencies.
384 Use @file{depfile} as output for -MD.
386 @item -print-search-dirs
387 Print the configured installation directory and a list of library
388 and include directories tcc will search.
395 Target specific options:
399 Use an algorithm for bitfield alignment consistent with MSVC. Default is
402 @item -mfloat-abi (ARM only)
403 Select the float ABI. Possible values: @code{softfp} and @code{hard}
406 Do not use sse registers on x86_64
409 Pass command line to the i386/x86_64 cross compiler.
413 Note: GCC options @option{-Ox}, @option{-fx} and @option{-mx} are
417 @c man begin ENVIRONMENT
418 Environment variables that affect how tcc operates.
424 A colon-separated list of directories searched for include files,
425 directories given with @option{-I} are searched first.
428 A colon-separated list of directories searched for libraries for the
429 @option{-l} option, directories given with @option{-L} are searched first.
438 @settitle Tiny C Compiler
452 @chapter C language support
456 TCC implements all the ANSI C standard, including structure bit fields
457 and floating point numbers (@code{long double}, @code{double}, and
458 @code{float} fully supported).
460 @section ISOC99 extensions
462 TCC implements many features of the new C standard: ISO C99. Currently
463 missing items are: complex and imaginary numbers.
465 Currently implemented ISOC99 features:
469 @item variable length arrays.
471 @item 64 bit @code{long long} types are fully supported.
473 @item The boolean type @code{_Bool} is supported.
475 @item @code{__func__} is a string variable containing the current
478 @item Variadic macros: @code{__VA_ARGS__} can be used for
479 function-like macros:
481 #define dprintf(level, __VA_ARGS__) printf(__VA_ARGS__)
485 @code{dprintf} can then be used with a variable number of parameters.
487 @item Declarations can appear anywhere in a block (as in C++).
489 @item Array and struct/union elements can be initialized in any order by
492 struct @{ int x, y; @} st[10] = @{ [0].x = 1, [0].y = 2 @};
494 int tab[10] = @{ 1, 2, [5] = 5, [9] = 9@};
497 @item Compound initializers are supported:
499 int *p = (int [])@{ 1, 2, 3 @};
501 to initialize a pointer pointing to an initialized array. The same
502 works for structures and strings.
504 @item Hexadecimal floating point constants are supported:
506 double d = 0x1234p10;
510 is the same as writing
512 double d = 4771840.0;
515 @item @code{inline} keyword is ignored.
517 @item @code{restrict} keyword is ignored.
520 @section GNU C extensions
522 TCC implements some GNU C extensions:
526 @item array designators can be used without '=':
528 int a[10] = @{ [0] 1, [5] 2, 3, 4 @};
531 @item Structure field designators can be a label:
533 struct @{ int x, y; @} st = @{ x: 1, y: 1@};
537 struct @{ int x, y; @} st = @{ .x = 1, .y = 1@};
540 @item @code{\e} is ASCII character 27.
542 @item case ranges : ranges can be used in @code{case}s:
546 printf("range 1 to 9\n");
549 printf("unexpected\n");
554 @cindex aligned attribute
555 @cindex packed attribute
556 @cindex section attribute
557 @cindex unused attribute
558 @cindex cdecl attribute
559 @cindex stdcall attribute
560 @cindex regparm attribute
561 @cindex dllexport attribute
562 @cindex nodecorate attribute
564 @item The keyword @code{__attribute__} is handled to specify variable or
565 function attributes. The following attributes are supported:
568 @item @code{aligned(n)}: align a variable or a structure field to n bytes
569 (must be a power of two).
571 @item @code{packed}: force alignment of a variable or a structure field to
574 @item @code{section(name)}: generate function or data in assembly section
575 name (name is a string containing the section name) instead of the default
578 @item @code{unused}: specify that the variable or the function is unused.
580 @item @code{cdecl}: use standard C calling convention (default).
582 @item @code{stdcall}: use Pascal-like calling convention.
584 @item @code{regparm(n)}: use fast i386 calling convention. @var{n} must be
585 between 1 and 3. The first @var{n} function parameters are respectively put in
586 registers @code{%eax}, @code{%edx} and @code{%ecx}.
588 @item @code{dllexport}: export function from dll/executable (win32 only)
590 @item @code{nodecorate}: do not apply any decorations that would otherwise be applied when exporting function from dll/executable (win32 only)
594 Here are some examples:
596 int a __attribute__ ((aligned(8), section(".mysection")));
600 align variable @code{a} to 8 bytes and put it in section @code{.mysection}.
603 int my_add(int a, int b) __attribute__ ((section(".mycodesection")))
610 generate function @code{my_add} in section @code{.mycodesection}.
612 @item GNU style variadic macros:
614 #define dprintf(fmt, args@dots{}) printf(fmt, ## args)
617 dprintf("one arg %d\n", 1);
620 @item @code{__FUNCTION__} is interpreted as C99 @code{__func__}
621 (so it has not exactly the same semantics as string literal GNUC
622 where it is a string literal).
624 @item The @code{__alignof__} keyword can be used as @code{sizeof}
625 to get the alignment of a type or an expression.
627 @item The @code{typeof(x)} returns the type of @code{x}.
628 @code{x} is an expression or a type.
630 @item Computed gotos: @code{&&label} returns a pointer of type
631 @code{void *} on the goto label @code{label}. @code{goto *expr} can be
632 used to jump on the pointer resulting from @code{expr}.
634 @item Inline assembly with asm instruction:
635 @cindex inline assembly
636 @cindex assembly, inline
639 static inline void * my_memcpy(void * to, const void * from, size_t n)
642 __asm__ __volatile__(
647 "1:\ttestb $1,%b4\n\t"
651 : "=&c" (d0), "=&D" (d1), "=&S" (d2)
652 :"0" (n/4), "q" (n),"1" ((long) to),"2" ((long) from)
660 TCC includes its own x86 inline assembler with a @code{gas}-like (GNU
661 assembler) syntax. No intermediate files are generated. GCC 3.x named
662 operands are supported.
664 @item @code{__builtin_types_compatible_p()} and @code{__builtin_constant_p()}
667 @item @code{#pragma pack} is supported for win32 compatibility.
671 @section TinyCC extensions
675 @item @code{__TINYC__} is a predefined macro to indicate that you use TCC.
677 @item @code{#!} at the start of a line is ignored to allow scripting.
679 @item Binary digits can be entered (@code{0b101} instead of
682 @item @code{__BOUNDS_CHECKING_ON} is defined if bound checking is activated.
687 @chapter TinyCC Assembler
689 Since version 0.9.16, TinyCC integrates its own assembler. TinyCC
690 assembler supports a gas-like syntax (GNU assembler). You can
691 deactivate assembler support if you want a smaller TinyCC executable
692 (the C compiler does not rely on the assembler).
694 TinyCC Assembler is used to handle files with @file{.S} (C
695 preprocessed assembler) and @file{.s} extensions. It is also used to
696 handle the GNU inline assembler with the @code{asm} keyword.
700 TinyCC Assembler supports most of the gas syntax. The tokens are the
705 @item C and C++ comments are supported.
707 @item Identifiers are the same as C, so you cannot use '.' or '$'.
709 @item Only 32 bit integer numbers are supported.
717 @item Integers in decimal, octal and hexa are supported.
719 @item Unary operators: +, -, ~.
721 @item Binary operators in decreasing priority order:
729 @item A value is either an absolute number or a label plus an offset.
730 All operators accept absolute values except '+' and '-'. '+' or '-' can be
731 used to add an offset to a label. '-' supports two labels only if they
732 are the same or if they are both defined and in the same section.
740 @item All labels are considered as local, except undefined ones.
742 @item Numeric labels can be used as local @code{gas}-like labels.
743 They can be defined several times in the same source. Use 'b'
744 (backward) or 'f' (forward) as suffix to reference them:
748 jmp 1b /* jump to '1' label before */
749 jmp 1f /* jump to '1' label after */
756 @cindex assembler directives
757 @cindex directives, assembler
758 @cindex align directive
759 @cindex skip directive
760 @cindex space directive
761 @cindex byte directive
762 @cindex word directive
763 @cindex short directive
764 @cindex int directive
765 @cindex long directive
766 @cindex quad directive
767 @cindex globl directive
768 @cindex global directive
769 @cindex section directive
770 @cindex text directive
771 @cindex data directive
772 @cindex bss directive
773 @cindex fill directive
774 @cindex org directive
775 @cindex previous directive
776 @cindex string directive
777 @cindex asciz directive
778 @cindex ascii directive
780 All directives are preceded by a '.'. The following directives are
784 @item .align n[,value]
785 @item .skip n[,value]
786 @item .space n[,value]
787 @item .byte value1[,...]
788 @item .word value1[,...]
789 @item .short value1[,...]
790 @item .int value1[,...]
791 @item .long value1[,...]
792 @item .quad immediate_value1[,...]
795 @item .section section
799 @item .fill repeat[,size[,value]]
802 @item .string string[,...]
803 @item .asciz string[,...]
804 @item .ascii string[,...]
807 @section X86 Assembler
810 All X86 opcodes are supported. Only ATT syntax is supported (source
811 then destination operand order). If no size suffix is given, TinyCC
812 tries to guess it from the operand sizes.
814 Currently, MMX opcodes are supported but not SSE ones.
817 @chapter TinyCC Linker
820 @section ELF file generation
823 TCC can directly output relocatable ELF files (object files),
824 executable ELF files and dynamic ELF libraries without relying on an
827 Dynamic ELF libraries can be output but the C compiler does not generate
828 position independent code (PIC). It means that the dynamic library
829 code generated by TCC cannot be factorized among processes yet.
831 TCC linker eliminates unreferenced object code in libraries. A single pass is
832 done on the object and library list, so the order in which object files and
833 libraries are specified is important (same constraint as GNU ld). No grouping
834 options (@option{--start-group} and @option{--end-group}) are supported.
836 @section ELF file loader
838 TCC can load ELF object files, archives (.a files) and dynamic
841 @section PE-i386 file generation
844 TCC for Windows supports the native Win32 executable file format (PE-i386). It
845 generates EXE files (console and gui) and DLL files.
847 For usage on Windows, see also tcc-win32.txt.
849 @section GNU Linker Scripts
850 @cindex scripts, linker
851 @cindex linker scripts
852 @cindex GROUP, linker command
853 @cindex FILE, linker command
854 @cindex OUTPUT_FORMAT, linker command
855 @cindex TARGET, linker command
857 Because on many Linux systems some dynamic libraries (such as
858 @file{/usr/lib/libc.so}) are in fact GNU ld link scripts (horrible!),
859 the TCC linker also supports a subset of GNU ld scripts.
861 The @code{GROUP} and @code{FILE} commands are supported. @code{OUTPUT_FORMAT}
862 and @code{TARGET} are ignored.
864 Example from @file{/usr/lib/libc.so}:
867 Use the shared library, but some functions are only in
868 the static library, so try that secondarily. */
869 GROUP ( /lib/libc.so.6 /usr/lib/libc_nonshared.a )
873 @chapter TinyCC Memory and Bound checks
875 @cindex memory checks
877 This feature is activated with the @option{-b} (@pxref{Invoke}).
879 Note that pointer size is @emph{unchanged} and that code generated
880 with bound checks is @emph{fully compatible} with unchecked
881 code. When a pointer comes from unchecked code, it is assumed to be
882 valid. Even very obscure C code with casts should work correctly.
884 For more information about the ideas behind this method, see
885 @url{http://www.doc.ic.ac.uk/~phjk/BoundsChecking.html}.
887 Here are some examples of caught errors:
891 @item Invalid range with standard string function:
899 @item Out of bounds-error in global or local arrays:
909 @item Out of bounds-error in malloc'ed data:
913 tab = malloc(20 * sizeof(int));
921 @item Access of freed memory:
925 tab = malloc(20 * sizeof(int));
937 tab = malloc(20 * sizeof(int));
946 @chapter The @code{libtcc} library
948 The @code{libtcc} library enables you to use TCC as a backend for
949 dynamic code generation.
951 Read the @file{libtcc.h} to have an overview of the API. Read
952 @file{libtcc_test.c} to have a very simple example.
954 The idea consists in giving a C string containing the program you want
955 to compile directly to @code{libtcc}. Then you can access to any global
956 symbol (function or variable) defined.
959 @chapter Developer's guide
961 This chapter gives some hints to understand how TCC works. You can skip
962 it if you do not intend to modify the TCC code.
964 @section File reading
966 The @code{BufferedFile} structure contains the context needed to read a
967 file, including the current line number. @code{tcc_open()} opens a new
968 file and @code{tcc_close()} closes it. @code{inp()} returns the next
973 @code{next()} reads the next token in the current
974 file. @code{next_nomacro()} reads the next token without macro
977 @code{tok} contains the current token (see @code{TOK_xxx})
978 constants. Identifiers and keywords are also keywords. @code{tokc}
979 contains additional infos about the token (for example a constant value
980 if number or string token).
984 The parser is hardcoded (yacc is not necessary). It does only one pass,
989 @item For initialized arrays with unknown size, a first pass
990 is done to count the number of elements.
992 @item For architectures where arguments are evaluated in
993 reverse order, a first pass is done to reverse the argument order.
999 The types are stored in a single 'int' variable. It was chosen in the
1000 first stages of development when tcc was much simpler. Now, it may not
1001 be the best solution.
1004 #define VT_INT 0 /* integer type */
1005 #define VT_BYTE 1 /* signed byte type */
1006 #define VT_SHORT 2 /* short type */
1007 #define VT_VOID 3 /* void type */
1008 #define VT_PTR 4 /* pointer */
1009 #define VT_ENUM 5 /* enum definition */
1010 #define VT_FUNC 6 /* function type */
1011 #define VT_STRUCT 7 /* struct/union definition */
1012 #define VT_FLOAT 8 /* IEEE float */
1013 #define VT_DOUBLE 9 /* IEEE double */
1014 #define VT_LDOUBLE 10 /* IEEE long double */
1015 #define VT_BOOL 11 /* ISOC99 boolean type */
1016 #define VT_LLONG 12 /* 64 bit integer */
1017 #define VT_LONG 13 /* long integer (NEVER USED as type, only
1019 #define VT_BTYPE 0x000f /* mask for basic type */
1020 #define VT_UNSIGNED 0x0010 /* unsigned type */
1021 #define VT_ARRAY 0x0020 /* array type (also has VT_PTR) */
1022 #define VT_VLA 0x20000 /* VLA type (also has VT_PTR and VT_ARRAY) */
1023 #define VT_BITFIELD 0x0040 /* bitfield modifier */
1024 #define VT_CONSTANT 0x0800 /* const modifier */
1025 #define VT_VOLATILE 0x1000 /* volatile modifier */
1026 #define VT_DEFSIGN 0x2000 /* signed type */
1028 #define VT_STRUCT_SHIFT 18 /* structure/enum name shift (14 bits left) */
1031 When a reference to another type is needed (for pointers, functions and
1032 structures), the @code{32 - VT_STRUCT_SHIFT} high order bits are used to
1033 store an identifier reference.
1035 The @code{VT_UNSIGNED} flag can be set for chars, shorts, ints and long
1038 Arrays are considered as pointers @code{VT_PTR} with the flag
1039 @code{VT_ARRAY} set. Variable length arrays are considered as special
1040 arrays and have flag @code{VT_VLA} set instead of @code{VT_ARRAY}.
1042 The @code{VT_BITFIELD} flag can be set for chars, shorts, ints and long
1043 longs. If it is set, then the bitfield position is stored from bits
1044 VT_STRUCT_SHIFT to VT_STRUCT_SHIFT + 5 and the bit field size is stored
1045 from bits VT_STRUCT_SHIFT + 6 to VT_STRUCT_SHIFT + 11.
1047 @code{VT_LONG} is never used except during parsing.
1049 During parsing, the storage of an object is also stored in the type
1053 #define VT_EXTERN 0x00000080 /* extern definition */
1054 #define VT_STATIC 0x00000100 /* static variable */
1055 #define VT_TYPEDEF 0x00000200 /* typedef definition */
1056 #define VT_INLINE 0x00000400 /* inline definition */
1057 #define VT_IMPORT 0x00004000 /* win32: extern data imported from dll */
1058 #define VT_EXPORT 0x00008000 /* win32: data exported from dll */
1059 #define VT_WEAK 0x00010000 /* win32: data exported from dll */
1064 All symbols are stored in hashed symbol stacks. Each symbol stack
1065 contains @code{Sym} structures.
1067 @code{Sym.v} contains the symbol name (remember
1068 an identifier is also a token, so a string is never necessary to store
1069 it). @code{Sym.t} gives the type of the symbol. @code{Sym.r} is usually
1070 the register in which the corresponding variable is stored. @code{Sym.c} is
1071 usually a constant associated to the symbol like its address for normal
1072 symbols, and the number of entries for symbols representing arrays.
1073 Variable length array types use @code{Sym.c} as a location on the stack
1074 which holds the runtime sizeof for the type.
1076 Four main symbol stacks are defined:
1081 for the macros (@code{#define}s).
1084 for the global variables, functions and types.
1087 for the local variables, functions and types.
1089 @item global_label_stack
1090 for the local labels (for @code{goto}).
1093 for GCC block local labels (see the @code{__label__} keyword).
1097 @code{sym_push()} is used to add a new symbol in the local symbol
1098 stack. If no local symbol stack is active, it is added in the global
1101 @code{sym_pop(st,b)} pops symbols from the symbol stack @var{st} until
1102 the symbol @var{b} is on the top of stack. If @var{b} is NULL, the stack
1105 @code{sym_find(v)} return the symbol associated to the identifier
1106 @var{v}. The local stack is searched first from top to bottom, then the
1111 The generated code and data are written in sections. The structure
1112 @code{Section} contains all the necessary information for a given
1113 section. @code{new_section()} creates a new section. ELF file semantics
1114 is assumed for each section.
1116 The following sections are predefined:
1121 is the section containing the generated code. @var{ind} contains the
1122 current position in the code section.
1125 contains initialized data
1128 contains uninitialized data
1130 @item bounds_section
1131 @itemx lbounds_section
1132 are used when bound checking is activated
1135 @itemx stabstr_section
1136 are used when debugging is active to store debug information
1138 @item symtab_section
1139 @itemx strtab_section
1140 contain the exported symbols (currently only used for debugging).
1144 @section Code generation
1145 @cindex code generation
1147 @subsection Introduction
1149 The TCC code generator directly generates linked binary code in one
1150 pass. It is rather unusual these days (see gcc for example which
1151 generates text assembly), but it can be very fast and surprisingly
1154 The TCC code generator is register based. Optimization is only done at
1155 the expression level. No intermediate representation of expression is
1156 kept except the current values stored in the @emph{value stack}.
1158 On x86, three temporary registers are used. When more registers are
1159 needed, one register is spilled into a new temporary variable on the stack.
1161 @subsection The value stack
1162 @cindex value stack, introduction
1164 When an expression is parsed, its value is pushed on the value stack
1165 (@var{vstack}). The top of the value stack is @var{vtop}. Each value
1166 stack entry is the structure @code{SValue}.
1168 @code{SValue.t} is the type. @code{SValue.r} indicates how the value is
1169 currently stored in the generated code. It is usually a CPU register
1170 index (@code{REG_xxx} constants), but additional values and flags are
1174 #define VT_CONST 0x00f0
1175 #define VT_LLOCAL 0x00f1
1176 #define VT_LOCAL 0x00f2
1177 #define VT_CMP 0x00f3
1178 #define VT_JMP 0x00f4
1179 #define VT_JMPI 0x00f5
1180 #define VT_LVAL 0x0100
1181 #define VT_SYM 0x0200
1182 #define VT_MUSTCAST 0x0400
1183 #define VT_MUSTBOUND 0x0800
1184 #define VT_BOUNDED 0x8000
1185 #define VT_LVAL_BYTE 0x1000
1186 #define VT_LVAL_SHORT 0x2000
1187 #define VT_LVAL_UNSIGNED 0x4000
1188 #define VT_LVAL_TYPE (VT_LVAL_BYTE | VT_LVAL_SHORT | VT_LVAL_UNSIGNED)
1194 indicates that the value is a constant. It is stored in the union
1195 @code{SValue.c}, depending on its type.
1198 indicates a local variable pointer at offset @code{SValue.c.i} in the
1202 indicates that the value is actually stored in the CPU flags (i.e. the
1203 value is the consequence of a test). The value is either 0 or 1. The
1204 actual CPU flags used is indicated in @code{SValue.c.i}.
1206 If any code is generated which destroys the CPU flags, this value MUST be
1207 put in a normal register.
1211 indicates that the value is the consequence of a conditional jump. For VT_JMP,
1212 it is 1 if the jump is taken, 0 otherwise. For VT_JMPI it is inverted.
1214 These values are used to compile the @code{||} and @code{&&} logical
1217 If any code is generated, this value MUST be put in a normal
1218 register. Otherwise, the generated code won't be executed if the jump is
1222 is a flag indicating that the value is actually an lvalue (left value of
1223 an assignment). It means that the value stored is actually a pointer to
1226 Understanding the use @code{VT_LVAL} is very important if you want to
1227 understand how TCC works.
1230 @itemx VT_LVAL_SHORT
1231 @itemx VT_LVAL_UNSIGNED
1232 if the lvalue has an integer type, then these flags give its real
1233 type. The type alone is not enough in case of cast optimisations.
1236 is a saved lvalue on the stack. @code{VT_LVAL} must also be set with
1237 @code{VT_LLOCAL}. @code{VT_LLOCAL} can arise when a @code{VT_LVAL} in
1238 a register has to be saved to the stack, or it can come from an
1239 architecture-specific calling convention.
1242 indicates that a cast to the value type must be performed if the value
1243 is used (lazy casting).
1246 indicates that the symbol @code{SValue.sym} must be added to the constant.
1250 are only used for optional bound checking.
1254 @subsection Manipulating the value stack
1257 @code{vsetc()} and @code{vset()} pushes a new value on the value
1258 stack. If the previous @var{vtop} was stored in a very unsafe place(for
1259 example in the CPU flags), then some code is generated to put the
1260 previous @var{vtop} in a safe storage.
1262 @code{vpop()} pops @var{vtop}. In some cases, it also generates cleanup
1263 code (for example if stacked floating point registers are used as on
1266 The @code{gv(rc)} function generates code to evaluate @var{vtop} (the
1267 top value of the stack) into registers. @var{rc} selects in which
1268 register class the value should be put. @code{gv()} is the @emph{most
1269 important function} of the code generator.
1271 @code{gv2()} is the same as @code{gv()} but for the top two stack
1274 @subsection CPU dependent code generation
1275 @cindex CPU dependent
1276 See the @file{i386-gen.c} file to have an example.
1281 must generate the code needed to load a stack value into a register.
1284 must generate the code needed to store a register into a stack value
1288 @itemx gfunc_param()
1290 should generate a function call
1292 @item gfunc_prolog()
1293 @itemx gfunc_epilog()
1294 should generate a function prolog/epilog.
1297 must generate the binary integer operation @var{op} on the two top
1298 entries of the stack which are guaranteed to contain integer types.
1300 The result value should be put on the stack.
1303 same as @code{gen_opi()} for floating point operations. The two top
1304 entries of the stack are guaranteed to contain floating point values of
1307 @item gen_cvt_itof()
1308 integer to floating point conversion.
1310 @item gen_cvt_ftoi()
1311 floating point to integer conversion.
1313 @item gen_cvt_ftof()
1314 floating point to floating point of different size conversion.
1316 @item gen_bounded_ptr_add()
1317 @item gen_bounded_ptr_deref()
1318 are only used for bounds checking.
1322 @section Optimizations done
1323 @cindex optimizations
1324 @cindex constant propagation
1325 @cindex strength reduction
1326 @cindex comparison operators
1327 @cindex caching processor flags
1328 @cindex flags, caching
1329 @cindex jump optimization
1330 Constant propagation is done for all operations. Multiplications and
1331 divisions are optimized to shifts when appropriate. Comparison
1332 operators are optimized by maintaining a special cache for the
1333 processor flags. &&, || and ! are optimized by maintaining a special
1334 'jump target' value. No other jump optimization is currently performed
1335 because it would require to store the code in a more abstract fashion.
1337 @unnumbered Concept Index
1344 @c texinfo-column-for-description: 32