Re: [Mingw-w64-public] [PATCH] headers: Add NTDDI_WIN10_NI in sdkddkver.h

在 2022-06-01 00:27, Biswapriyo Nath 写道: 0001-headers-Add-NTDDI_WIN10_NI-in-sdkddkver.h.patch From 32d8a4fce8171d82162129d049965ad981e34da7 Mon Sep 17 00:00:00 2001 From: Biswapriyo Nath Date: Tue, 31 May 2022 21:57:04 +0530 Subject: [PATCH] headers: Add NTDDI_WIN10_NI in sdkddkver.h Signed-off

[Mingw-w64-public] Detect presence of Windows implementations of inet_ntop and inet_npton

Hi, In the Perl source, we hard code our own implementation of inet_ntop() and inet_pton(). This results in a fatal compile-time error if the Windows (ws2tcpip.h) implementation is also present. I'm therefore looking for a portable way of detecting whether the compiler is a mingw-w64 one && the W

Re: [Mingw-w64-public] [PATCH] winpthreads: Move .seh_handlerdata to the end of the catch region

在 2022-06-01 16:18, Martin Storsjö 写道: This matches what was done in 9718ecee1b95297b789b75a0be51bfd5905bcdcd for crt/crtexe.c. The .seh_handlerdata directive forces writing the .xdata entry immediately. On aarch64, the length of the function gets fixed at that point, and if the .seh_handlerdata

[Mingw-w64-public] [PATCH] winpthreads: Move .seh_handlerdata to the end of the catch region

This matches what was done in 9718ecee1b95297b789b75a0be51bfd5905bcdcd for crt/crtexe.c. The .seh_handlerdata directive forces writing the .xdata entry immediately. On aarch64, the length of the function gets fixed at that point, and if the .seh_handlerdata directive is emitted too soon, it won't c