Re: [Tinycc-devel] randomly failing tests

On 2022-12-07 16:12:22 +0100, Vincent Lefevre wrote: > The cause seems to be that the generated executable name is fixed > to "a.exe" instead of depending on the test name: > > 113_btdll.test: T1 = \ > $(TCC) -bt $1 -shared -D DLL=1 -o a1$(DLLSUF) && \ > $(TCC) -bt $1 -shared -D DLL=2 -o a

Re: [Tinycc-devel] randomly failing tests

On 2022-12-07 16:06:27 +0100, Vincent Lefevre wrote: > Tests are failing randomly on Debian/x86_64: > > [...] > Test: 107_stack_safe... > Test: 108_constructor... > Test: 109_float_struct_calling... > Test: 110_average... > Test: 111_conversion... > Test: 112_backtrace... > --- 108_constructor.exp

[Tinycc-devel] randomly failing tests

Tests are failing randomly on Debian/x86_64: [...] Test: 107_stack_safe... Test: 108_constructor... Test: 109_float_struct_calling... Test: 110_average... Test: 111_conversion... Test: 112_backtrace... --- 108_constructor.expect 2022-12-07 15:57:51.358297673 +0100 +++ 108_constructor.output

Re: [Tinycc-devel] Non PIC-code and TCC's GOT strategy for TCC_OUTPUT_MEMORY

On 05.12.2022 22:10, Macoy Madson wrote: Hi, I'm working on using TCC as the core of run-time modifiable applications. I am using TCC as a library, and compiling/linking straight to memory, i.e. tcc_set_output_type(state, TCC_OUTPUT_MEMORY). I have mob c03d59e. I was having issues with static