Hi
Why do you need it? Is there native arm64 version of the dlls (I've seen some announcements but is it already available)? Or is it only for winelib applications?
Thanks, Piotr
Hi Piotr,
On Mon, 31 Jul 2017, Piotr Caban wrote:
Why do you need it? Is there native arm64 version of the dlls (I've seen some announcements but is it already available)?
I don't have the native arm64 version of the DLLs, but I do have corresponding import libs.
The public win10 SDK (from already 2 years ago) contains arm64 import libraries. There's no publicly available MSVC compiler targeting arm64 yet though (and I don't have any private one either), but I'm working on trying to bootstrap a build/test env for win/arm64.
Clang as compiler and lld as linker have gotten to the point now that they are pretty usable for building things for win/arm64, able to build pretty large real world projects - but the only environment I have for actually running the code is in wine so far.
In normal app code, built with clang and linked to the public win10 sdk import libs, I'm ending up with references to fabsf in api-ms-win-crt-math-l1-1-0.dll.
The part of the patch that touches msvcr80/90/100/110/120 was only done for consistency - in practice it's probably only needed for ucrtbase.dll.
(Similarly the case of -arch=arm in msvcr80/90/100 for arm probably isn't necessary since there's afaik nobody referencing those on arm, but it's probably easiest to keep them for consistency - that's why I'm adding it to all of them here as well.)
// Martin
-
Martin Storsjö -
Piotr Caban