Skip to content

[QST] GemmOperation configuration name change in 4.0. Is this intended? #2435

@henrylhtsang

Description

@henrylhtsang

What is your question?

Hi, I noticed there is a change in ops name in CUTLASS 4.0.

For example (not one to one example):

Before:
cutlass3x_sm90_tensorop_s64x256x16gemm_bf16_bf16_f32_void_bf16_128x256x64_1x2x1_0_ttn_align8_warpspecialized_cooperative_epi_tma

After:
cutlass3x_sm90_tensorop_gemm_bf16_bf16_f32_void_bf16_128x128x64_1x1x1_0_ttn_align8_cpasync_warpspecialized_cooperative_epi_nosmem

Is this intended?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions