Avi Halachmi (:avih) 4fccaf6124 Revert "build c2str.exe with the host compiler; default it to gcc if cross prefix given"
This reverts commit 41fa74fc84.

Reasons for the revert:

1. The commit message is lacking and the use case is not obvious.
   At the very least a concrete example of use case should be given
   (likely cross-building tcc on platform X for running on platform Y),
   followed by an issue description in such use case, and fix descr.
   (e.g. "On platform X, when running ./configure ... && make ..., the
   build fails because whatever. this commit does Y and fixes it").

2. assign_opt is used incorrectly: 1st arg must be --OPTNAME=VALUE
   but it's not. The only thing it does is unconditional host_cc=gcc
   if --cross-prefix=... is used - no need for "assign_opt" at all.

3. cross-building tcc currently has several triggers: build/target
   cpu differ, or build/target OS differ, or --cross-prefix=... is
   used, but that commit only covers the --cross-prefix=... case.
   It's possible that it's intentional to only cover one case, but
   if so then it's not explained why.

4. The var name host_cc is likely incorrect and probably meant to be
   "native_cc", judging by the assigned value "gcc".

5. "gcc" is used unconditionally in such case, without any way to use
   a different native compiler (assuming that's indeed the goal).
   A better approach is likely supporting --native-cc=... option which
   defaults to $cc (which already defaults to "gcc") _before_
   $cross_prefix is added in-front.
2026-01-18 09:04:54 +02:00
2026-01-10 13:46:23 +01:00
2025-12-17 20:22:08 +01:00
2026-01-10 13:46:23 +01:00
2026-01-10 13:46:23 +01:00
2025-11-26 11:10:10 +13:00
2024-11-30 20:05:02 +01:00
2026-01-10 13:46:23 +01:00
2026-01-10 13:46:23 +01:00
2024-11-09 08:04:45 +01:00
2026-01-10 13:46:23 +01:00
2026-01-10 13:46:23 +01:00
2025-08-22 19:14:44 +02:00
2026-01-10 13:46:23 +01:00
2024-06-11 14:26:34 +02:00
2017-05-07 21:38:09 -07:00
2003-05-24 14:18:56 +00:00
2022-05-05 09:10:37 +02:00
2025-07-14 08:27:14 +02:00
2026-01-10 13:46:23 +01:00
2025-12-30 20:15:35 +01:00
2022-12-13 11:34:54 +01:00
2026-01-10 13:46:23 +01:00
2026-01-06 12:11:51 +01:00
2025-10-09 13:08:33 +02:00
2024-08-11 15:18:36 +02:00
2026-01-10 13:46:23 +01:00
2026-01-10 13:46:23 +01:00
2025-12-23 06:46:22 +01:00
2026-01-10 13:46:23 +01:00
2026-01-10 13:46:23 +01:00
2025-09-08 17:22:21 +02:00
2026-01-10 13:46:23 +01:00
2026-01-10 13:46:23 +01:00
2025-08-18 20:43:52 +02:00
2025-07-21 00:48:51 -03:00
2025-12-03 17:21:00 +02:00
2026-01-10 13:46:23 +01:00
2026-01-10 13:46:23 +01:00

Tiny C Compiler - C Scripting Everywhere - The Smallest ANSI C compiler
-----------------------------------------------------------------------

Features:
--------

- SMALL! You can compile and execute C code everywhere, for example on
  rescue disks.

- FAST! tcc generates machine code for i386, x86_64, arm, aarch64 or
  riscv64.  Compiles and links about 10 times faster than 'gcc -O0'.

- UNLIMITED! Any C dynamic library can be used directly. TCC is
  heading toward full ISOC99 compliance. TCC can of course compile
  itself.

- SAFE! tcc includes an optional memory and bound checker. Bound
  checked code can be mixed freely with standard code.

- Compile and execute C source directly. No linking or assembly
  necessary. Full C preprocessor included.

- C script supported : just add '#!/usr/local/bin/tcc -run' at the first
  line of your C source, and execute it directly from the command
  line.

Documentation:
-------------

1) Installation on Linux, BSD variants or macOS hosts:

   ./configure
   make
   make test
   make install

   Notes: On BSD hosts, gmake should be used instead of make.
   For Windows read tcc-win32.txt.

makeinfo must be installed to compile the doc.  By default, tcc is
installed in /usr/local/bin.  ./configure --help  shows configuration
options.


2) Introduction

We assume here that you know ANSI C. Look at the example ex1.c to know
what the programs look like.

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 -run' 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) Examples

ex1.c: simplest example (hello world). Can also be launched directly
as a script: './ex1.c'.

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
because standard headers are being used ! As for ex1.c, can also be launched
directly as a script: './ex4.c'.

ex5.c: 'hello world' with standard glibc headers.

tcc.c: TCC can of course compile itself. Used to check the code
generator.

tcctest.c: auto test for TCC which tests many subtle possible bugs. Used
when doing 'make test'.

4) Full Documentation

Please read tcc-doc.html to have all the features of TCC.  Additional
information for the Windows port is in tcc-win32.txt.

License:
-------

TCC is distributed under the GNU Lesser General Public License (see
COPYING file).

Fabrice Bellard.
Description
Unofficial mirror of mob development branch
Readme 11 MiB
Languages
C 95.4%
Assembly 2.4%
Makefile 0.9%
C++ 0.5%
Shell 0.3%
Other 0.5%