Skip to content

CUDA quantized kernels: correct block layouts, cache keys and precision #5323

Open
4 of 7 issues completed

Description

@noahgift

Scope: Correctness of the CUDA quantized kernels: Q5_K block layout, FP8 GEMM stale activations and FP16 overflow, RMSNorm epsilon in the cache key, stale Q8_1 activation caches, unknown quant types decoded as Q4_K, IQ kernels on Blackwell, the DP4A path, and a registry that refuses any unregistered kernel.

Why it matters: Each of these makes the GPU answer differ from the CPU answer or from llama.cpp, silently. A wrong-but-fast kernel is worse than a slow one.

Done when: Every (qtype, layout, arch) kernel in use is in the registry, and the GPU-vs-CPU parity test passes on lambda (sm_89) and gx10 (Blackwell) for every quant type in the model ladder.

Epic: #3994. Folded under triage rule 7b (2026-10-14): each row below was its own issue, closed as not planned and kept here as a sub-ticket. Reopen an issue when its work starts or its PR opens.

Sub-tickets

Folded in by the 0.73–0.76 triage (2026-10-31)

These were open tickets; to keep the repo at 100 open or fewer they now live here as checkboxes. Reopen a ticket when this epic schedules it.

Activity

  1. added this to the 0.71.0 milestone on Oct 14, 2026
  2. added
    bugSomething isn't working
    P1High priority
    on Oct 14, 2026
  3. modified the milestones: 0.71.0, 0.72.0, 0.73.0 on Oct 14, 2026
  4. noahgift commented on Oct 22, 2026

    @noahgift
    MemberAuthor

    Tracked in #3598 (triage 2026-10-22).

  5. modified the milestones: 0.73.0, 0.72.0 on Oct 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High prioritybugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions