tinycc/config.h.in

#define CONFIG_TCCDIR "${CONFIG_TCCDIR}"
#define TCC_VERSION "${TCC_VERSION}"

#cmakedefine CONFIG_WIN32
#cmakedefine CONFIG_WIN64
#cmakedefine CONFIG_TCC_BCHECK
#cmakedefine CONFIG_TCC_ASSERT
Sorted out CMake on x86-64 and fixed silly XMM# bug introduced when working on Win64 stdargs. I removed the XMM6/7 registers from the register list because they are not used on Win64 however they are necessary for parameter passing on x86-64. I have now restored them but not marked them with RC_FLOAT so they will not be used except for parameter passing. 2013-04-26 05:30:53 +08:00			`#define CONFIG_TCCDIR "${CONFIG_TCCDIR}"`
Added CMake build system (to facilitate Win64 builds) Win32 build and tests work under CMake, however I haven't added install code yet. Win64 build fails due to chkstk.S failing to assemble. 2013-04-21 18:20:20 +08:00			`#define TCC_VERSION "${TCC_VERSION}"`

			`#cmakedefine CONFIG_WIN32`
			`#cmakedefine CONFIG_WIN64`
Improved variable length array support. VLA storage is now freed when it goes out of scope. This makes it possible to use a VLA inside a loop without consuming an unlimited amount of memory. Combining VLAs with alloca() should work as in GCC - when a VLA is freed, memory allocated by alloca() after the VLA was created is also freed. There are some exceptions to this rule when using goto: if a VLA is in scope at the goto, jumping to a label will reset the stack pointer to where it was immediately after the last VLA was created prior to the label, or to what it was before the first VLA was created if the label is outside the scope of any VLA. This means that in some cases combining alloca() and VLAs will free alloca() memory where GCC would not. 2013-04-28 03:39:34 +08:00			`#cmakedefine CONFIG_TCC_BCHECK`
			`#cmakedefine CONFIG_TCC_ASSERT`