PantheonSim / GPUs / AMD Radeon RX 9070 XT

Simulated AMD Radeon RX 9070 XT: a GPU profile for CUDA and ROCm testing

PantheonSim, the GPU simulator for CUDA and ROCm, simulates the AMD Radeon RX 9070 XT (RDNA 4, gfx1201) as the profile amd/rx9070xt. A Radeon RX 9070 XT (Navi 48, 64 compute units), the RDNA 4 part among the profiles. Its profile is built from public documents and not yet measured against a physical card.

The profile at a glance

These are the numbers a program can ask this simulated GPU, and the values rocm-smi and amd-smi show for it. They come from the profile file in the simulator's repository, pinned to one commit of it.

PropertyValue
Profile idamd/rx9070xt
Vendor and architectureAMD, RDNA 4
GPU targetgfx1201
Device memory16.0 GiB, GDDR
Multiprocessors (as HIP reports them)32
Wavefront size32
Max threads per multiprocessor2048
Shared memory per block (opt-in maximum)64 KiB
L2 cache8 MiB
Power limit (profile)304 W
Maximum clocks (profile)2970 MHz shader, 2518 MHz memory
ECC memoryno
PCIe link reportedGen5 x16
Tensor or matrix coresyes
Verified (measured on a physical card)not yet measured

What this GPU is for

A Radeon RX 9070 XT (Navi 48, 64 compute units), the RDNA 4 part among the profiles.

RDNA 4 is the Radeon RX 9000 generation, gfx1201. Kernels run 32 lanes to a wave, as HIP builds them for it.

Among the 10 AMD profiles it ranks 7th by device memory (16.0 GiB) and 8th by multiprocessors as HIP counts them (32), counting the largest as first.

Is this profile verified?

No. This profile is marked not verified: it is built from public documents only, and nothing in it was measured on a physical card. Some figures are derived or copied from the nearest profile where the vendor publishes none, so treat them as approximate, and memory sizes as upper bounds. The profile file itself calls some of its values placeholders. Programs still run on it, and it still answers every call as the architecture's rules require, but a value such as a clock or a limit may differ from a real card's.

Simulate this GPU

Build the simulator (see the docs) or open the playground, then:

hipcc --offload-arch=gfx1201 my_app.hip -o my_app
vgpu run --gpu amd/rx9070xt ./my_app
vgpu shell -y --gpu amd/rx9070xt --count 4 --rocm 7.1.0
vgpu info --gpu amd/rx9070xt

Build for this card's own gfx target, gfx1201. A program built for another target is refused by name, as the real runtime refuses it, and hipErrorNoBinaryForGpu means exactly this.

To use it every time, put gpu: amd/rx9070xt in a pantheonsim.yaml settings file, or in a GitHub Actions job give the PantheonSim action gpu: amd/rx9070xt (see CUDA and HIP tests in GitHub Actions). The simulator checks behaviour and has no timing model, so a run on a physical GPU before a release still counts. The ROCm and HIP guide explains the rest.

Where the numbers come from

Each profile file begins with a note on its sources. This is the note for AMD Radeon RX 9070 XT, as written in the file:

Source note for amd/rx9070xt

Values from public AMD documentation. verified: false means nothing here has been confirmed by hardware characterization yet, treat as placeholders. RDNA4: gfx1201 (Navi 48), a consumer card whose kernels run 32 lanes to a wave, as HIP builds them for it. HIP counts its compute units in pairs (workgroup processors): 32 of the card's 64.

The GPU index lists every profile, and this one is not yet measured.

Other AMD profiles: