On Monday 16 February 2026 22:32:39 Jacek Caban wrote:
> On 2/16/26 22:15, Pali Rohár wrote:
> > -// F_X86_ANY - function available on i386 and x86_64
> > +// F_X86_ANY - function available on i386, x86_64 and arm64_ec
>
>
> It is usually spelled arm64ec, without the underscore.
I see, I can simply fix this.
>
> I do not really see the point of the rest of the series, though. Why would
> we want to support something like that?
Because without those changes, it is causing compile errors.
LIU Hao run the previous version on CI and CI throw errors. He wrote me:
`src_msvcrt64` isn't compiled into the ARM64EC library, which ends up in
undefined references:
https://github.com/lhmouse/mingw-w64/actions/runs/21061471379/job/60568582713#step:6:420
As those mentioned symbols are available in Windows 10 x64 msvcrt.dll
library, so as I understood it is not needed to provide arm64ec
emulation for them (as there is no pre-Win10 arm64ec version). So I
chose to use native symbols in arm64ec builds and dynamic load with
fallback to emulation for x64 builds.
It is wrong what I have tried to achieve? Or did I understand it
incorrectly? I can update or improve changes, or better describe them if
needed.
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
