NVIDIA / NVIDIA/cutlass

Example 64 (Ada FP8 grouped GEMM) refuses capable GPUs via exact CC 8.9 gate

Open Beginner friendly
#3,524 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

CUTLASS C++
Dominant language
C++
Stars
10.5k
Forks
2.1k
Avg merge
3d 11h
Merged PRs (30d)
7

Description

Description

examples/64_ada_fp8_gemm_grouped/ada_fp8_gemm_grouped.cu (~line 1107) gates execution on exactly compute capability 8.9:

if (!(properties.major == 8 && properties.minor == 9)) {
    std::cerr << "... requires a device of compute capability 89." ...

The grouped FP8 kernels here compile cleanly for newer architectures, and the sibling example 58_ada_fp8_gemm uses the inclusive form:

if (properties.major < 8 || (properties.major == 8 && properties.minor < 9))

On an RTX 5060 Ti (sm_120a, CUDA 12.8.1) the stock binary exits immediately with the capability message; with the gate relaxed to the sibling's form the example builds and runs to completion including device-reference verification (Passed). Example 64 is therefore refusing capable hardware for no functional reason.

Suggested fix

Use the same major*10+minor < 89 / major < 8 || (major == 8 && minor < 9) inclusive check as example 58.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Open examples/64_ada_fp8_gemm_grouped/ada_fp8_gemm_grouped.cu around line 1107 and compare its compute-capability check with the inclusive check in example 58_ada_fp8_gemm. Update the gate to accept architectures at or above the stated minimum, then build and run Example 64 to confirm device-reference verification reports “Passed” on newer capable hardware.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend, performance
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
91/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.