Re: [Tinycc-devel] Newest TCC builds broken on legacy Windows versions on GCC 4.5.2

[Eric Raible]

If build with:

-DCONFIG_RUNMEM_ALIGNED=0

I'm hoping you'd be good to go.

On linux one would:

./configure --extra-cflags=-DCONFIG_RUNMEM_ALIGNED=0

On windows I'm not sure, but perhaps augmenting the lines in

win32/build-tcc.bat to look like this would do the same:

set D32=-DTCC_TARGET_PE -DTCC_TARGET_I386 -DCONFIG_RUNMEM_ALIGNED=0
set D64=-DTCC_TARGET_PE -DTCC_TARGET_X86_64 -DCONFIG_RUNMEM_ALIGNED=0

- Eric

On Sat, Feb 24, 2024 at 7:29 AM Dog Dog <andreywilliamsjeffrey@gmail.com> wrote:

I get an error about missing entry point _aligned_free in msvcrt.dll. Since the newest builds are labeled as TCC version 0.9.28 RC one could wait until after an official TCC version 0.9.28 to break compatibility with legacy Windows versions.

The newest builds of TCC are broken on Windows 2000, Windows NT 4.0, Windows NT 3.51, Windows Me, Windows 98 and Windows 95. I realize that old versions of Windows can't be supported forever and that is an amazing level of compatibility for builds prior to recent builds.

The problem started with this build:

https://repo.or.cz/tinycc.git/commit/7b9f19eaab7e568a7c7a42725da812377a588f50

_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel