stop tracking build/, like the other ggml kernels
Marc Sun
a03d80d
`build/` is already gitignored here, and `ggml-attn` and `ggml-gated-delta-net` never tracked it: the
artifacts a client downloads live on the kernel repo's `v1` branch, which `build-and-upload` writes.
Keeping a second copy in git only creates two things to keep in step, and they had already drifted --
what shipped was stamped 09da59d, what was committed here 1f05408.
rebuild metal for get_rows, and track artifacts by glob
Marc Sun
e6e7898
The published `.so` predates `get_rows`, so a client that asks for it gets an AttributeError and
falls back to unpacking whole tensors. Rebuilt from a clean tree, so the module carries the commit
it was built from rather than a `_dirty` name.
`.gitattributes` listed every artifact by path, one line per rebuild, and the entries outlived the
files. One glob covers whatever hash the next build stamps in.
Built from a clean tree at 0becb0a, so the variants carry that revision rather than a dirty stamp.
104 tests pass against torch212-metal on this machine.
Refresh the Metal builds after the command-buffer fix
Verified against the pure-torch reference dequantizer: dequantize is bit-exact
for q8_0/q4_K/q5_K/q6_K and mul_mat_vec agrees to ~1e-6 relative on all four.
GGUF kernels: dequantize + fused gemv over packed blocks
