Re: [Mingw-w64-public] [gcc-13.0.1] weird issue with 32-bit setjmp.h

2023-04-16 Thread sisyphus
On Mon, Apr 17, 2023 at 1:02 AM Martin Storsjö wrote: > mingw-w64 never defined USE_NO_MINGW_SETJMP_TWO_ARGS. Do the perl sources > define it? > Yes - and for quite a long time. (But only for 32-bit builds of course.) https://github.com/Perl/perl5/blob/blead/dist/threads/threads.xs begins with

Re: [Mingw-w64-public] [gcc-13.0.1] weird issue with 32-bit setjmp.h

2023-04-16 Thread Martin Storsjö
On Mon, 17 Apr 2023, sisyphus wrote: My question therefore is: If the 32-bit 12.2.0 version of setjmp.h works fine with 32-bit gcc-13.0.1, then why was it altered ? Maybe that's a dumb question - hopefully not sufficiently dumb as to cause offence. We made a change to simplify code, in a plac

[Mingw-w64-public] [gcc-13.0.1] weird issue with 32-bit setjmp.h

2023-04-16 Thread sisyphus
Hi, I was having difficulty building threaded 32-bit perl using gcc-13.0.1. No problem building threaded 64-bit perl with gcc-13.0.1. Also no problem building threaded perls (both 32-bit and 64-bit) with gcc-12.2.0 or earlier. I tried fixing the issue by making a few modifications to dist/threads.