Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Misc. bug: MUL_MAT: wrong results, exceeds tolerance; gfx1200 HIP/ROCm; f16 + deterministic.

Open
#31,111 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
46/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp

Research direction

Start by running the reported test-backend-ops command with the given HIP build configuration on gfx1200 to confirm the failing MUL_MAT case. Then trace the HIP backend path for f16-by-f32 matrix multiplication and inspect its precision and determinism behavior. Done means the reported case passes within the stated tolerance; the issue does not identify a root cause or relevant source file.

Written by the indexing model from the issue text.

Description

bug-unconfirmed
Name and Version

0.7.0-dev, ggml commit a37cc46

Operating systems

Linux

Which llama.cpp modules do you know to be affected?

Test code, Other (Please specify in the next section)

Command line
./build-hip/bin/test-backend-ops test -j 1 -o MUL_MAT -p 'n=2105344'
Problem description & steps to reproduce

In MUL_MAT on HIP/ROCm gfx1200, I got wrong results, no crash. This happened on ROCm 7.1.1, Ubuntu 26.04, and RX 9060 XT. ERR = 0.004255280 > 0.000500000 , 8.5x tolerance. Case: MUL_MAT(type_a=f16,type_b=f32,m=16,n=2105344,k=32,bs=[1,1],nr=[1,1],per=[0,1,2,3],k_v=0,o=1,src_overlap=0,m_v=0,pad=0). Deterministic: 0.004253291 on October 21st, 0.004255280 on October 23rd, same to three significant figures across runs with different random inputs. So it's a systematic precision problem, not a flaky race. Not claimed: No root cause. Repro reports 0/1 tests passed. Build Command:

cmake -S . -B build-hip -DGGML_HIP=ON -DGPU_TARGETS=gfx1200
-DLLAMA_BUILD_TESTS=ON -DCMAKE_BUILD_TYPE=Release
cmake --build build-hip --target test-backend-ops -j 12

First Bad Commit

Don’t know, present at a37cc46, haven’t bisected.

Relevant log output
[MUL_MAT] ERR = 0.004255280 > 0.000500000 MUL_MAT(type_a=f16,type_b=f32,m=16,n=2105344,k=32,bs=[1,1],nr=[1,1],per=[0,1,2,3],k_v=0,o=1,src_overlap=0,m_v=0,pad=0): FAIL
Dominant language
C++
Stars
132k
Forks
24.6k
Avg merge
2d 2h
Merged PRs (30d)
501

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ggml-org/llama.cpp

All issues in ggml-org/llama.cpp

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.