Skip to content

[CK] Disable DPP kernels, address build fail: not a valid operand#2256

Merged
mhalk merged 1 commit into
ROCm:aomp-devfrom
mhalk:amd/dev/mhalkenh/fix/dpp-kernel-build-fail
Jun 12, 2026
Merged

[CK] Disable DPP kernels, address build fail: not a valid operand#2256
mhalk merged 1 commit into
ROCm:aomp-devfrom
mhalk:amd/dev/mhalkenh/fix/dpp-kernel-build-fail

Conversation

@mhalk

@mhalk mhalk commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Workaround, disabling the corresponding kernels during build.

Motivation

Observed CK build fails across multiple major architectures during nightly CI.

Technical Details

Added CMake flag which disables the corresponding DPP kernels.

Test Plan

Execute CK build with previously failing CK SHA and compiler.

Test Result

Successful build via CI scripts.

Submission Checklist

@mhalk mhalk requested review from Kewen12 and jplehr June 12, 2026 11:39
@mhalk mhalk force-pushed the amd/dev/mhalkenh/fix/dpp-kernel-build-fail branch from 642712a to cae775a Compare June 12, 2026 11:40
@jplehr

jplehr commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Is it a fix or a workaround? :)

@mhalk mhalk changed the title [CK] Fix DPP kernel related build fail: not a valid operand [CK] Disable DPP kernels, address build fail: not a valid operand Jun 12, 2026
Workaround, disabling the corresponding kernels during build.
@mhalk mhalk force-pushed the amd/dev/mhalkenh/fix/dpp-kernel-build-fail branch from cae775a to 976827f Compare June 12, 2026 11:44
@mhalk

mhalk commented Jun 12, 2026

Copy link
Copy Markdown
Contributor Author

Is it a fix or a workaround? :)

Fair, fair ... It is a workaround which "fixes" the build fail ...

@mhalk mhalk merged commit e3e43b6 into ROCm:aomp-dev Jun 12, 2026
1 check passed
@mhalk mhalk deleted the amd/dev/mhalkenh/fix/dpp-kernel-build-fail branch June 12, 2026 11:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants