[Mingw-w64-public] [PATCH 3/3] crt: Build __guard_dispatch_icall_dummy on ARM64EC

--- There???s an alternative way to handle this, see: https://github.com/llvm/llvm-project/pull/135280 It would work in this case, but I???m not convinced it???s the right approach overall. While extending the assembler to allow setting the flag is straightforward, handling the different relocation

[Mingw-w64-public] [PATCH 2/3] crt: Move __guard_dispatch_icall_dummy to separated file

In preparation for building as x86_64 on ARM64EC. --- mingw-w64-crt/Makefile.am | 3 ++- mingw-w64-crt/cfguard/guard_dispatch.S| 11 +++ mingw-w64-crt/cfguard/mingw_cfguard_support.c | 8 3 files changed, 13 insertions(+), 9 deletions(-) create mode

Re: [Mingw-w64-public] [PATCH 2/2] crt: Add ARM64EC setjmp and longjmp implementation

On 12.04.2025 00:14, Jacek Caban wrote: On 11.04.2025 23:34, Jacek Caban wrote: Based on Wine code by Alexandre Julliard. ---   mingw-w64-crt/Makefile.am    |   8 ++-   mingw-w64-crt/misc/arm64ec/longjmp.c |  30   mingw-w64-crt/misc/arm64ec/setjmp.c  | 104 ++

[Mingw-w64-public] [PATCH 1/3] crt: Build scanf.S as an x86_64 object on ARM64EC

A proper ARM64EC implementation would be tricky, as it would need to handle a different calling convention and possibly use exit thunks for imported functions. Instead, we can simply use the x86_64 version. --- This series, together with setjmp/longjmp, finally allow building unmodified mingw-w64-c