Stripped down TinyCC fork for StupidOS
Before VC2005, the time macros (time, time_t, localtime, etc) were 32 bit on 32 bit platforms, but they became 64 in VC2005. This works even on XP 32 (_time64 etc do exist in XP32 - and in tcc). However, tv_sec in struct timeval (which for msvc is in winsock2.h) remains 32 bit to this day on 32 bit platforms, and dlls which were not recompiled remain with time 32, possibly at the API boundary. Due to these, and maybe more, mingw w64 decided to keep the time macros 32 bit on 32 bit platforms, with __MINGW_USE_VC2005_COMPAT override (which does nothing in mingw w64 except time -> time64). It's not perfect, but it allows some existing code to easily switch to 64 bit time without redefining time etc, e.g. used by libressl: https://github.com/libressl/portable/blob/master/README.mingw.md Before, it was impossible to enable the 64 bit time macros in tcc 32. This commit adds support for __MINGW_USE_VC2005_COMPAT in tcc as well, which, like in mingw w64, affects only the 32->64 time macros, and is a cheap way to get 64 bit time in existing code in some 32 bit apps. The additional #ifndef _USE_32BIT_TIME_T is unrelated to the override, and avoids a warning (and nothing else) when the code explicitly defines it - which is allowed in MSVC, and also guarded in mingw w64. Relevant current quote from the libressl link above: ------- >8 --------- Why the -D__MINGW_USE_VC2005_COMPAT flag on 32-bit systems? An ABI change introduced with Microsoft Visual C++ 2005 (also known as Visual C++ 8.0) switched time_t from 32-bit to 64-bit. It is important to build LibreSSL with 64-bit time_t whenever possible, because 32-bit time_t is unable to represent times past 2038 (this is commonly known as the Y2K38 problem). If LibreSSL is built with 32-bit time_t, when verifying a certificate whose expiry date is set past 19 January 2038, it will be unable to tell if the certificate has expired or not, and thus take the safe stance and reject it. In order to avoid this, you need to build LibreSSL (and everything that links with it) with the -D__MINGW_USE_VC2005_COMPAT flag. This tells MinGW-w64 to use the new ABI. 64-bit systems always have a 64-bit time_t and are not affected by this problem. |
||
---|---|---|
.github/workflows | ||
examples | ||
include | ||
lib | ||
tests | ||
win32 | ||
.gitignore | ||
arm-asm.c | ||
arm-gen.c | ||
arm-link.c | ||
arm-tok.h | ||
arm64-asm.c | ||
arm64-gen.c | ||
arm64-link.c | ||
c67-gen.c | ||
c67-link.c | ||
Changelog | ||
CodingStyle | ||
coff.h | ||
configure | ||
conftest.c | ||
COPYING | ||
dwarf.h | ||
elf.h | ||
i386-asm.c | ||
i386-asm.h | ||
i386-gen.c | ||
i386-link.c | ||
i386-tok.h | ||
il-gen.c | ||
il-opcodes.h | ||
libtcc.c | ||
libtcc.h | ||
Makefile | ||
README | ||
RELICENSING | ||
riscv64-asm.c | ||
riscv64-gen.c | ||
riscv64-link.c | ||
riscv64-tok.h | ||
stab.def | ||
stab.h | ||
tcc-doc.texi | ||
tcc.c | ||
tcc.h | ||
tccasm.c | ||
tcccoff.c | ||
tccdbg.c | ||
tccelf.c | ||
tccgen.c | ||
tcclib.h | ||
tccmacho.c | ||
tccpe.c | ||
tccpp.c | ||
tccrun.c | ||
tcctok.h | ||
tcctools.c | ||
texi2pod.pl | ||
TODO | ||
USES | ||
VERSION | ||
x86_64-asm.h | ||
x86_64-gen.c | ||
x86_64-link.c |
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 optimized x86 code. No byte code overhead. Compile, assemble and link about 7 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 a i386/x86_64/arm/aarch64/riscv64 Linux/macOS/FreeBSD/NetBSD/OpenBSD hosts. ./configure make make test make install Notes: For FreeBSD, NetBSD and OpenBSD, 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 is available for the Windows port in tcc-win32.txt. License: ------- TCC is distributed under the GNU Lesser General Public License (see COPYING file). Fabrice Bellard.