Re: [Mingw-w64-public] Internal compiler error specific to MinGW when using -fstack-clash-protection and __attribute__((noreturn))

LIU Hao wrote: 在 2023-02-04 20:51, Théo Cavignac 写道: Sorry, I misclicked and sent an half written mail. So as I tried to expose, I am using MinGW with following configuration: This looks like a GCC issue. Reported here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108673 Workaround:

Re: [Mingw-w64-public] Internal compiler error specific to MinGW when using -fstack-clash-protection and __attribute__((noreturn))

在 2023-02-04 20:51, Théo Cavignac 写道: Sorry, I misclicked and sent an half written mail. So as I tried to expose, I am using MinGW with following configuration: This looks like a GCC issue. Reported here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108673 -- Best regards, LIU Hao

Re: [Mingw-w64-public] Internal compiler error specific to MinGW when using -fstack-clash-protection and __attribute__((noreturn))

Sorry, I misclicked and sent an half written mail. So as I tried to expose, I am using MinGW with following configuration: Using built-in specs. COLLECT_GCC=x86_64-w64-mingw32-gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-w64-mingw32/12.2.0/lto-wrapper Target: x86_64-w64-mingw32

[Mingw-w64-public] Internal compiler error specific to MinGW when using -fstack-clash-protection and __attribute__((noreturn))

Hello, As implied by the subject I isolated an internal compiler error that is specific to MinGW (stock GCC Minimal code /*   /usr/bin/x86_64-w64-mingw32-gcc \     -O2 -fstack-clash-protection -c \     -freport-bug \     -o f.o f.c  */ void exit(int)