Re: [Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly handled by installed signal handler.

[Christian Jullien]

Hum!?
My machine is a quite old Core i7 processor which has not all modern
instructions (like AVX2).
Could it be related to a generated instruction which does not exist on my
processor.
Pelle's C latest C compiler has a similar issue. Without specific option, it
sometimes generates AVX2 instructions which makes my machine to hand.

M2c.

I'll try to debug this further...

C

-----Original Message-----
From: Tinycc-devel [mailto:address@hidden
On Behalf Of Michael Matz
Sent: Monday, April 08, 2019 19:43
To: address@hidden; address@hidden
Subject: Re: [Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly
handled by installed signal handler.

Hello,

On Mon, 8 Apr 2019, Christian Jullien wrote:

> c:\tmp>tcc -m64 signal.c && signal
> 
> Waiting for SIGSEGV  <<= program terminates after this print!!

Works for me under wine64:

% ./x86_64-win32-tcc -m64 -B. -Iwin32/include -L. signal.c -Lwin32/lib
% file signal.exe
signal.exe: PE32+ executable (console) x86-64 (stripped to external PDB), 
for MS Windows

(so it's really x86_64), and then:

% wine signal.exe
Waiting for SIGSEGV
Got signal 11!! Want to exit? [y/n] y
Exiting from handler...

(answering 'n' works as expected too).

So I can't reproduce (with a quite different environment though).  As 
you're probably using the same headers as me (the ones delivered with 
tinycc) it would seem that the differences can't be coming from there, so
the difference is coming from the runtime environment from Windows proper.  
I can't really speculate what that might be and how to amend TCC to care 
for this; the code generation in principle works as demonstrated above, 
some detail is missing :-/


Ciao,
Michael.

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