-
Notifications
You must be signed in to change notification settings - Fork 257
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
[Bug]: backend cannot select in neon code #1883
Comments
Сorresponding xnnpack can be found here: |
Can you attach this? It'd let me reproduce the issue without checking-out the xnnpack repo. |
I'm facing this too.
|
I am struggling to reproduce this as we are using custom build system. |
This is my reproducer: |
Does it reproduce with the toolchain in r26 canary? I can reproduce with r25 but r26 and ToT clang give several errors that look like below:
This maybe a forward compatibility issue with the pre-processed headers. |
It might be easier to work with a preprocessed file(.I). |
As discussed in XNNPACK issue, it looks like the issue does not reproduce with clang16. |
Description
Hi.
I am trying to update xnnpack to 2023-04-18 / 71f70de09ca17f125d3c24ccceeb12045a674d0c in order to update tensorflow-lite to 2.12.0.
Unfortunately clang for android segfaults when compiling
src/bf16-gemm/gen/bf16-gemm-1x4c8-minmax-neonbf16-bfdot.c
for android-armv7a.I am able to reproduce this:
I have tested NDK's r25b and r25c, but the segfault still persists and there is no way to fix this.
I have tested ndk r25b and r25c, but the issue persists.
Classic clang 14.0.x does not seems to be affected by the problem.
Upstream bug
No response
Commit to cherry-pick
No response
Affected versions
r25
Canary version
No response
Host OS
Linux
Host OS version
Ubuntu 20.04
Affected ABIs
armeabi-v7a
The text was updated successfully, but these errors were encountered: