-
Notifications
You must be signed in to change notification settings - Fork 536
the clang compiler does not support '-march=armv8.2-a+bf16' when build xnnpack for android #6924
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
Comments
Getting the same error
|
@digantdesai do you know a work around for this issue with clang? |
It looks like a similar issue was filed in XNNPACK and the suggested solution was to disable bf16 with -DXNNPACK_ENABLE_ARM_BF16=OFF (google/XNNPACK#3618). I guess using GCC might also work, but maybe there's a better option with clang |
Thanks! That works |
Thanks @metascroy for the suggestion. Yeah I guess the right way would be to check (by tracking minimum_supported_version for clang in this case) if the compiler supports, this and enable only when it does. And That said BF16 was enabled by LLVM a while ago (2020?), and is the reason to enable by default. |
Follow the tutorial to build xnnpack runtime lib for android with NDK r19 and meet such errors:
[ 91%] Building C object backends/xnnpack/third-party/XNNPACK/CMakeFiles/microkernels-all.dir/src/bf16-gemm/gen/bf16-gemm-1x4c8-minmax-neonbf16-bfmlal.c.o
[ 91%] Building C object backends/xnnpack/third-party/XNNPACK/CMakeFiles/microkernels-all.dir/src/bf16-gemm/gen/bf16-gemm-1x4c8-minmax-neonbf16-bfdot.c.o
[ 91%] Building C object backends/xnnpack/third-party/XNNPACK/CMakeFiles/microkernels-all.dir/src/bf16-gemm/gen/bf16-gemm-1x8c2-minmax-neonbf16-bfdot-lane-ld128.c.o
clang: error: the clang compiler does not support '-march=armv8.2-a+bf16'
gmake[2]: *** [backends/xnnpack/third-party/XNNPACK/CMakeFiles/microkernels-all.dir/build.make:43241: backends/xnnpack/third-party/XNNPACK/CMakeFiles/microkernels-all.dir/src/bf16-gemm/gen/bf16-gemm-1x4c8-minmax-neonbf16-bfmlal.c.o] Error 1
The text was updated successfully, but these errors were encountered: