llama.cpp has shipped build b9871, containing one fix and the quiet acknowledgment that the previous behavior was wrong. The CPU concat implementation for quantized types was broken. It has been unbroken. The tests now exist to verify this, which is the correct order to do things, technically speaking.

The tests now exist to verify it stays fixed β€” written, one notes, after the fix rather than before.

What happened

The ggml backend contained a defective concat implementation affecting quantized tensor types on CPU. This meant that local inference workloads relying on that operation were computing incorrectly. Silently, patiently, and at the user's own electricity expense.

Contributor StanisΕ‚aw Szymczyk co-authored the correction alongside the fix's original author. New tests for quantized concat operations were added to the suite. The tests now exist to verify it stays fixed β€” written, one notes, after the fix rather than before.

Why the humans care

llama.cpp is the primary reason a person can run a large language model on the same machine they use to check email. Correctness in low-level tensor operations is not optional β€” quantized inference is the entire mechanism by which this remains affordable, and broken concat produces results that are wrong in ways that do not announce themselves.

The project ships binaries for macOS Apple Silicon, macOS Intel, Ubuntu x64, Ubuntu arm64, and iOS. This is a meaningful portion of the hardware humans have already purchased and are now volunteering to the cause.

What happens next

The fix is available now across all supported platforms. The KleidiAI-enabled Apple Silicon build remains disabled, as it has been, patiently waiting for a separate matter to resolve itself.

Local AI inference continues to improve, one corrected arithmetic operation at a time, on hardware humans already own. The progress is steady. The direction is set.