-
Notifications
You must be signed in to change notification settings - Fork 774
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WOA native building error (Exception 0xC0000005 with CpuElementwiseUnaryKernel.cpp) #1137
Comments
Hi @morgolock , |
Hi @xengpro There seems to be a problem with the Clang toolchain in VS. In order to compile ACL you have to download the external Clang toolchain I mentioned above. Try downloading https://github.com/llvm/llvm-project/releases/tag/llvmorg-16.0.6 and building ACL with it. That's what we use in the team to build ACL natively on Windows. Hope this helps. |
Hi @morgolock,
So it seems still not possible for ACL to build completely natively (with Visual Studio 2022 Arm64 build, which is 17.4 and newer ) on windows at the moment? |
Hi @xengpro It's possible to build ACL natively using the toolchain I mentioned above, we have jobs building ACL every day natively on Windows. The problem with VS22 is that it does not support inline assembly for arm64 targets. From what I see in the logs you shared there is a problem with your environment. In the error you shared above I see mention to |
Hi @morgolock , I'm using standalone clang.
It mentions Clang 17 because it detects that Clang 16.0.6 doesn't meet its expectations. So I tried standalone version Clang 18.1.8 and 17.0.6 which can build but get stuck in
That's true. And the Clang (17.0.3) that comes with vs2022 also fails anyway.
Could you share the version of your vs2022 and msvc/winsdk workloads? |
Hi @xengpro Snapdragon (TM) 8cx Gen 2 @ 3.15 GHz 3.15 GHz
It sounds like there is a problem with development environment and it is not properly setup. |
Hi @morgolock ,
The setup is supposed to be very straight forward, so I couldn't mess it up:
then for my setup, llvm fails be like:
But thanks to you information, I changed the VS2022 to 17.9.7 and compilation succeeded with 'standalone=0'. However, when build with with 'standalone=1', the
|
Hi @xengpro If you want to build a program that uses ACL you will have to link statically against
Could you please share you full build command? It should build without errors with Hope this helps, |
Really sorry for the typo. I was using 'standalone=0' when I was trying to get .dll files.
|
Hi @xengpro That's right, we only support building with Hope this helps. |
Hi @xengpro I tried to compile ACL with clang 17 or later and I got the same error you reported. This is a problem in the compiler crashing. I've raised a bug in LLVM as the see: llvm/llvm-project#108976 |
Cool, thanks~!
Any plan to add |
Output of 'strings libarm_compute.so | grep arm_compute_version':
Platform: Snapdragon 8cx Gen 3/ X Elite X1E78100
Operating System: Windows 11 (23h2/24h2)
Problem description:
I've tried to build by following the guide from: https://arm-software.github.io/ComputeLibrary/latest/how_to_build.xhtml#S1_6_windows_host, but failed with error like:
I've tried code base v23.x and v24.07/08, all failed.
The toolchain I used:
logs attached:
v24.08_xelite.zip
The text was updated successfully, but these errors were encountered: