Skip to content

CustomKernels don't need tuning arguments - #5320

Merged
AlexBrownAMD merged 1 commit into
GemmFromAnywherefrom
users/alexbrownamd/GemmFromAnywhere_NoSizeMapping
Mar 11, 2026
Merged

AlexBrownAMD merged 1 commit into
GemmFromAnywherefrom
users/alexbrownamd/GemmFromAnywhere_NoSizeMapping

Conversation

@AlexBrownAMD

Copy link
Copy Markdown
Contributor

Update the way CustomKernel info gets stored in a solution to improve default build, and avoid having to come up with equivalent tuning arguments to describe external kernels.

@AlexBrownAMD
AlexBrownAMD requested a review from a team as a code owner March 10, 2026 23:00
@AlexBrownAMD
AlexBrownAMD merged commit 3c80e98 into GemmFromAnywhere Mar 11, 2026
9 of 12 checks passed
@AlexBrownAMD
AlexBrownAMD deleted the users/alexbrownamd/GemmFromAnywhere_NoSizeMapping branch March 11, 2026 16:52
jinchen62 pushed a commit that referenced this pull request Mar 25, 2026
Update the way CustomKernel info gets stored in a solution to improve
default build, and avoid having to come up with equivalent tuning
arguments to describe external kernels.
jinchen62 pushed a commit that referenced this pull request Apr 1, 2026
Update the way CustomKernel info gets stored in a solution to improve
default build, and avoid having to come up with equivalent tuning
arguments to describe external kernels.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant