ROCm / ROCm/aiter

[Issue]: seems batch gemm does not support some specific shapes?

Open
#426 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
565
Forks
585
Avg merge
3d 4h
Merged PRs (30d)
366

Description

Problem Description

shapes like A=[bs, m, k] B=[k, n]

Operating System

linux

CPU

AMD

GPU

mi300

ROCm Version

6.3.2

ROCm Component

No response

Steps to Reproduce

No response

(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support

No response

Additional Information

No response

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

No source file, test, or reproduction command is provided. Start by reproducing batch GEMM with A=[bs, m, k] and B=[k, n] on Linux with an AMD MI300 and ROCm 6.3.2, then locate the batch GEMM entry point and its shape tests. Done means the shape support boundary is established and the failing case is handled or clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, python
Domain
backend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.