Skip to content

tflite: always fetch neon2sse instead of gating per-arch - #31

Merged
Koen Kooi (koenkooi) merged 1 commit into
qualcomm-linux:mainfrom
koenkooi:koen/tflite-neon2sse-always-fetch
Sep 10, 2026
Merged

Koen Kooi (koenkooi) merged 1 commit into
qualcomm-linux:mainfrom
koenkooi:koen/tflite-neon2sse-always-fetch

Conversation

@koenkooi

Copy link
Copy Markdown
Contributor

Summary

  • The NEON-to-SSE translation shim (neon2sse) was only fetched via :class-target:x86/:class-target:x86-64 SRC_URI/SRCREV_FORMAT overrides, with do_configure guarding the symlink on a directory-exists check. Every new target arch that needs the shim would require yet another override — the same whack-a-mole pattern just fixed for the litert recipe in litert: add x86_64 support #29.
  • Fetch neon2sse unconditionally in the base SRC_URI/SRCREV_FORMAT, drop the arch-gated overrides, and simplify the do_configure:prepend() symlink to an unconditional ln -sf matching the other third-party symlinks in that function.

Test plan

  • Verified with a clean kas-container build for both qemuarm64 and qemux86-64 (this change was validated together with the analogous litert fix in litert: add x86_64 support #29's testing).

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com

SRC_URI/SRCREV_FORMAT only pulled in the NEON-to-SSE translation shim
on x86/x86-64 via :class-target overrides, and do_configure guarded
the matching symlink with a directory-exists check. That means every
new target arch that could use the shim needs its own override added.

Fetch it unconditionally instead: it's a small git repo and harmless
to fetch on arches that don't use it, matching the same fix already
applied to the litert recipe.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Signed-off-by: Koen Kooi <koen.kooi@oss.qualcomm.com>
@koenkooi
Koen Kooi (koenkooi) merged commit 21e7b36 into qualcomm-linux:main Sep 10, 2026
15 checks passed
@koenkooi
Koen Kooi (koenkooi) deleted the koen/tflite-neon2sse-always-fetch branch September 10, 2026 11:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant