which clang source of bf16 GEMM kernel
Open
Nobody has claimed this yet.
module: kernels
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
Which source path called for BF16 GEMM kernel(vbfdotq_f32)?
- system clang path: /usr/lib/llvm-14/lib/clang/14.0.0/include/arm_neon.h
- clang of android ndk path: /android-ndk-r27c/toolchains/llvm/prebuilt/linux-x86_64/lib/clang/18/include/arm_neon.h
cc @larryliu0820 @manuelcandales
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the vbfdotq_f32 BF16 GEMM kernel and compare the two arm_neon.h paths named in the issue: the system Clang 14 header and the Android NDK r27 Clang 18 header. Inspect the relevant toolchain selection and establish which header is used; done means the selected source path is identified and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- build-system, embedded-iot, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100