Re: [Mingw-w64-public] [PATCH 2/2] headers: Add IMAGE_ARM64_RUNTIME_FUNCTION_ENTRY_XDATA

2023-04-18 Thread LIU Hao
在 2023/4/19 05:08, Martin Storsjö 写道: Also add enums for interpreting some fields in the arm64 pdata. These have been present in WinSDK since 10.0.19041.0. Curiously, there's no similar structs for interpreting the ARM xdata (but the format is well documented, just like for ARM64). Signed-off-

[Mingw-w64-public] [PATCH 1/2] headers: Define IMAGE_RUNTIME_FUNCTION_ENTRY for aarch64

2023-04-18 Thread Martin Storsjö
We've had a definition of IMAGE_ARM64_RUNTIME_FUNCTION_ENTRY since 0f9569488ba7e48472183765a7ae6555ed990f4a in 2018, but we missed the definition of the generic IMAGE_RUNTIME_FUNCTION_ENTRY to point to the arch specific version of it. The shorter names RUNTIME_FUNCTION and PRUNTIME_FUNCTION alread

[Mingw-w64-public] [PATCH 2/2] headers: Add IMAGE_ARM64_RUNTIME_FUNCTION_ENTRY_XDATA

2023-04-18 Thread Martin Storsjö
Also add enums for interpreting some fields in the arm64 pdata. These have been present in WinSDK since 10.0.19041.0. Curiously, there's no similar structs for interpreting the ARM xdata (but the format is well documented, just like for ARM64). Signed-off-by: Martin Storsjö --- mingw-w64-heade

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

2023-04-18 Thread sisyphus
On Tue, Apr 18, 2023 at 8:26 PM Martin Storsjö wrote: The most robust way forward would, IMO, be to just stop trying to redefine > it, and stop undeffing/overriding the system's setjmp() function, since > that's what it is going to be using in the end anyway. Yes - and the elegance and simplici

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

2023-04-18 Thread Martin Storsjö
On Tue, 18 Apr 2023, sisyphus wrote: The mingw-w64 commit that removed use of USE_NO_MINGW_SETJMP_TWO_ARGS would have affected the former, but I don't see why it would affect the latter; if the latter works as intended there would be no need for USE_NO_MINGW_SETJMP_TWO_ARGS in the first place.