Upgrade llama.cpp from b10423 to b10456

[bernardladenthin]

Summary

• Upgrade pinned llama.cpp version from b10423 to b10456 across all configuration files and documentation
• Verified all 6 patches apply cleanly and pass full test suite (485/485 ctest passing)
• No breaking changes to project source code; all affected upstream APIs are either inert in this codebase or internal to upstream-compiled translation units

Details

This upgrade spans 8 intermediate tags (b10423→b10430→b10436→b10441→b10447→b10448→b10454→b10455→b10456) and includes:

• Server queue refactoring (#27041, #27133): on_new_task callback signature changed and yield_to_queue() added, but only upstream's server-context.cpp registers this callback — no project source is affected
• Model additions: Kimi-K3 text model and MiniMaxText01/MiniMaxM1 architectures (purely additive, internal to upstream TUs)
• API additions: ggml_ssm_scan() gained a trailing int64_t K parameter, but it is only called inside llama.cpp's own translation units
• Internal header changes: mtmd-image.h and models/models.h (internal helpers) changed, but public headers mtmd.h and mtmd-helper.h are byte-identical across the range
• Backend improvements: SYCL optimizations, Vulkan fixes, LoRA bounds-checking, reasoning effort support
• Vendored dependency: cpp-httplib 0.53.0 → 0.53.1 (source-compatible point release; behavioral fixes are internal)

Of the 22 upstream headers the project includes directly, only 3 changed:

• tools/server/server-queue.h: Breaking callback signature change (inert — upstream's sole registrant)
• ggml/include/ggml.h: ggml_ssm_scan() parameter addition (inert — called only in upstream TUs)
• tools/mtmd/mtmd-helper-common.h: size_t widening (no signature change)

All other included headers (llama.h, common.h, chat.h, arg.h, mtmd.h, mtmd-helper.h, tools/server/*.h) are byte-identical b10423→b10456.

Test plan

• All 6 patches re-verified against clean b10456 checkout; sequential git apply succeeded at every intermediate tag
• Full local verification: fresh configure + cmake --build + ctest 485/485 passing
• CI is green on this branch
• Docs updated (CLAUDE.md, README.md, breaking-changes history)

Related issues / PRs

Upstream: llama.cpp #27041, #27133, #27018, #27034, #27071, #27103, #27099, #27075, #27130, #27056, #27176, #27160, #26953, #26623, #26653, #26185, #25686, #25268

Checklist

• I have read CONTRIBUTING.md and CODE_OF_CONDUCT.md
• My commits follow Conventional Commits
• No security-sensitive changes

https://claude.ai/code/session_01JYGrvcgi2cnh6gg8D24uC7

[claude]

Review Summary

✅ Code Quality: Excellent

This is a well-executed version upgrade PR that demonstrates meticulous attention to the project's upgrade discipline:

Verification Checklist — All Items Complete

• ✅ CMakeLists.txt — GIT_TAG updated to b10456
• ✅ LlamaCppVersion.java — Constant and Javadoc updated (2 locations)
• ✅ README.md — Badge and link updated
• ✅ CLAUDE.md — Version reference updated (4 occurrences: line 9, 493, 533, 1360)
• ✅ No stale b10423 references left in configuration files
• ✅ Breaking-changes history correctly documents the entire range (b10423→b10456)

Upstream API Analysis — Thorough & Accurate

The breaking-changes documentation is exceptionally comprehensive, covering all 8 intermediate tags and correctly identifying that:

• The only 3 headers with changes across the range are inert in this project
• server-queue.h's callback signature change: no project source uses this API (upstream-only)
• ggml_ssm_scan() parameter addition: called only in upstream TUs
• mtmd-helper-common.h size_t widening: no signature change

Testing

• ✅ All 6 patches verified to apply cleanly at target
• ✅ Full test suite green (485/485 ctest passing)
• ✅ No undefined references or link failures

Documentation

The PR description and breaking-changes history provide exceptional detail — future maintainers have everything needed to understand the upgrade rationale and scope.

Result: No issues found. This upgrade is clean and follows all established procedures.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud