Skip to content

[release/2.12] Add gfx1100, gfx1101, gfx1151 to hipBLASLt preferred archs#3316

Merged
jithunnair-amd merged 1 commit into
release/2.12from
hipblaslt-preferred-gfx1100-gfx1151-2.12
Jun 25, 2026
Merged

[release/2.12] Add gfx1100, gfx1101, gfx1151 to hipBLASLt preferred archs#3316
jithunnair-amd merged 1 commit into
release/2.12from
hipblaslt-preferred-gfx1100-gfx1151-2.12

Conversation

@nemanjaudovic

Copy link
Copy Markdown

Add gfx1100, gfx1101, gfx1151 to hipBLASLt preferred archs

@rocm-repo-management-api

rocm-repo-management-api Bot commented Jun 17, 2026

Copy link
Copy Markdown

Jenkins build for 44652b848b5c4bb03b3b4f9c6bafd94dfc21e286 commit finished as FAILURE
Links: Pipeline Overview / Build artifacts / Test Results

@jithunnair-amd jithunnair-amd changed the title Add gfx1100, gfx1101, gfx1151 to hipBLASLt preferred archs [release/2.12] Add gfx1100, gfx1101, gfx1151 to hipBLASLt preferred archs Jun 24, 2026
@jithunnair-amd

Copy link
Copy Markdown
Collaborator

@nemanjaudovic Is there any context you can provide to substantiate why we can now include these additional archs in the hipblasLt preferred archs? Either hipblasLT documentation or testing results from your end?

@jithunnair-amd

Copy link
Copy Markdown
Collaborator

@nemanjaudovic Is there any context you can provide to substantiate why we can now include these additional archs in the hipblasLt preferred archs? Either hipblasLT documentation or testing results from your end?

Context in a comment from a sister PR: #3317 (comment)

@jithunnair-amd jithunnair-amd merged commit 2cd6ef5 into release/2.12 Jun 25, 2026
4 of 7 checks passed
@jithunnair-amd jithunnair-amd deleted the hipblaslt-preferred-gfx1100-gfx1151-2.12 branch June 25, 2026 13:34
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.

2 participants