You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add an SVE256+I8MM Q8 validation lane and close the #149 audit notes #145
Patch 0003:validate_wrapper.yml still has a v0.7.0 row in every lane, and v0.7.0 segfaults without 0003 (exit 139 on real weights, [0.17.1] Retire carried patch 0003 on llama.cpp v0.8.0 #140). Once core has shipped on v0.8.0 (0.17.1), drop the v0.7.0 rows and delete 0003. The retirement test in tests/test_llama_cpp_patches.py reads the 0003 series entry and must change with it.
SVE256+I8MM Q8 kernels: no lane runs them (docs/v080_android_isa_qualification.md). A lane needs QEMU with sve-default-vector-length=32,sme=off, or Neoverse V1 hardware.
#149 audit notes:tools/expected_tts_model_types.py returns 0xa if upstream renames common_chat_get_tts_prompt, so a probe going false with it would pass a release without LFM3 (add a floor for known tags); the linux_dlopen_smoke.c comparison has no failure-path test; no mask assertion on macOS, iOS or Android; COMMAND_ERROR_IS_FATAL needs CMake 3.19 against a 3.14 minimum; the tool's read_text() has no encoding=; llamadart_tts_lfm3_smoke reports "no backends are loaded" in a Release build until backends are preloaded.
Triage: P3. No user-facing failure: the patch only applies to v0.7.0 builds, and the kernel gap is qualification coverage. Starts after core 0.17.1 ships.
First bullet done: #185 (merged as b9985944) deletes patch 0003 and the v0.7.0LLAMADART_UPSTREAMS row, with the matching tests and docs. CI passed 34/34 at head 679f9339. Two KleidiAI source downloads returned HTTP 504 on the first attempt and passed on rerun.
The issue's trigger was met: core v0.17.1–v0.17.5 pin native v0.8.0-1, v0.18.0 pins v0.8.0-3, and main pins v0.9.0. Patch 0004 and the v0.8.0 row stay, because core 0.18 still ships on v0.8.0.
Still open here: the SVE256+I8MM Q8 lane and the #149 audit notes.
changed the title [-]Retire patch 0003 and the v0.7.0 validation rows after core leaves v0.7.0; add an SVE256+I8MM Q8 lane[/-][+]Add an SVE256+I8MM Q8 validation lane and close the #149 audit notes[/+]on Nov 8, 2026
Activity
leehack commentedon Oct 30, 2026
Triage: P3. No user-facing failure: the patch only applies to v0.7.0 builds, and the kernel gap is qualification coverage. Starts after core 0.17.1 ships.
Retire patch 0003 and the v0.7.0 qualification row (#185)
leehack commentedon Nov 8, 2026
First bullet done: #185 (merged as
b9985944) deletes patch 0003 and thev0.7.0LLAMADART_UPSTREAMSrow, with the matching tests and docs. CI passed 34/34 at head679f9339. Two KleidiAI source downloads returned HTTP 504 on the first attempt and passed on rerun.The issue's trigger was met: core v0.17.1–v0.17.5 pin native
v0.8.0-1, v0.18.0 pinsv0.8.0-3, and main pinsv0.9.0. Patch 0004 and thev0.8.0row stay, because core 0.18 still ships on v0.8.0.Still open here: the SVE256+I8MM Q8 lane and the #149 audit notes.
[-]Retire patch 0003 and the v0.7.0 validation rows after core leaves v0.7.0; add an SVE256+I8MM Q8 lane[/-][+]Add an SVE256+I8MM Q8 validation lane and close the #149 audit notes[/+]leehack commentedon Nov 8, 2026
Patch 0003 and the v0.7.0 row were retired in #185 (b998594). This issue now tracks only the SVE256+I8MM Q8 lane and the remaining #149 audit notes.