--- 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 types would be more problematic. That wouldn???t matter for this particular case, but having proper build system support seems more flexible in general.
mingw-w64-crt/Makefile.am | 2 ++ 1 file changed, 2 insertions(+) diff --git a/mingw-w64-crt/Makefile.am b/mingw-w64-crt/Makefile.am index 283ecdffc..04b61c429 100644 --- a/mingw-w64-crt/Makefile.am +++ b/mingw-w64-crt/Makefile.am @@ -1135,6 +1135,7 @@ src_libmingwexarm64=\ if ARM64EC src_libmingwexarm64+=crt/chpe.S +src_libmingwexarm64_x64=libarm64/cfguard/guard_dispatch.x86_64.o endif # These intrinsics are target independent: @@ -2529,6 +2530,7 @@ libarm64_libmingw32_a_SOURCES = $(src_libmingw32) libarm64_LIBRARIES += libarm64/libmingwex.a libarm64_libmingwex_a_CPPFLAGS=$(CPPFLAGSARM64) $(extra_include) $(AM_CPPFLAGS) libarm64_libmingwex_a_SOURCES = $(src_libmingwex) $(src_libmingwexarm64) $(src_dfp_math) +libarm64_libmingwex_a_LIBADD=$(src_libmingwexarm64_x64) libarm64_LIBRARIES += libarm64/libmoldname.a libarm64_libmoldname_a_CPPFLAGS=$(CPPFLAGSARM64) $(extra_include) $(AM_CPPFLAGS) -- 2.49.0
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
