Is our TinyCC build on Windows setting -march correctly?

[Jarred-Sumner]

Where are we setting C flags when building TinyCC? How are we making sure that baseline builds are working correctly with TinyCC?

bun/scripts/build-tinycc.ps1

Lines 20 to 25 in 830af23

	Run clang-cl -DTCC_TARGET_PE -DTCC_TARGET_X86_64 config.h -DC2STR -o c2str.exe conftest.c
	Run .\c2str.exe .\include\tccdefs.h tccdefs_.h
	# TODO: -MT
	Run clang-cl libtcc.c -o tcc.obj "-DTCC_TARGET_PE" "-DTCC_TARGET_X86_64" "-O2" "-W2" "-Zi" "-MD" "-GS-" "-c"
	Run lib "tcc.obj" "-OUT:tcc.lib"

It feels highly suspicious that so many of the "Illegal instruction" errors include a stack trace that points to TinyCC. Either something is going wrong while generating the stacktrace, or something is wrong with the TinyCC build.

Related issues:

• Illegal instruction bun #10435
• Illegal instruction on windows x64 baseline #10460
• bun upgrade Error #10545
• bun install -g <package> #10546
• bun install ERROR #10547
• segfaults on any commands #10578
• Illegal instruction on Windows - Bun crash #10583
• Bun has crashed on bun install #10615
• bun crash #10629
• Same segfault problem #10700
• Illegal instruction at address when using bun install #10755
• Another segfault when running commands #10756
• Bun crashes on Windows 2019 Datacenter and 2022 Standard #10788
• Illegal instruction at address 0x7FF684285541 #10790
• bun install error on 1.1.7 #10798
• crashed on running command bun install #10841
• panic(thread 14156): Illegal instruction at address 0x7FF65688FA41 #10853

[jexroid]

will this problem fixed in the next version?