Skip to content

Conversation

@NaveenElumalaiAMD
Copy link
Contributor

@NaveenElumalaiAMD NaveenElumalaiAMD commented Jul 30, 2025

… (#207)"

This reverts a line in the commit b5b297e --no-enumerate, because of reported performance regression from the staging team.

@NaveenElumalaiAMD NaveenElumalaiAMD requested a review from a team as a code owner July 30, 2025 18:31
minsukim-amd pushed a commit that referenced this pull request Jul 31, 2025
Change package description to ROCm

[ROCm/hipBLAS commit: b6c67fa]
@NaveenElumalaiAMD NaveenElumalaiAMD changed the title Revert "Re-apply Windows compatibility fixes to command construction.… remove options --no-enumerate Jul 31, 2025
@TorreZuk
Copy link
Contributor

Looks like the other changes to use cmake -E env also broke the build with old cmake versions. See #1006 but let us deal with that separately.

Anyone on tensile team can say why --no-enumerate gave us a corrupt build?

Copy link
Contributor

@TorreZuk TorreZuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need a tensile team member to approve and hopefully comment

@davidd-amd davidd-amd merged commit 68a380c into develop Aug 1, 2025
12 of 13 checks passed
@davidd-amd davidd-amd deleted the users/nelumala/revert-commit-b5b297e branch August 1, 2025 18:41
assistant-librarian bot pushed a commit to ROCm/Tensile that referenced this pull request Aug 1, 2025
@bstefanuk
Copy link
Contributor

--no-enumerate is not an impactful flag, this shouldn't affect the build. Safe to merge.

@TorreZuk
Copy link
Contributor

TorreZuk commented Aug 1, 2025

--no-enumerate is not an impactful flag, this shouldn't affect the build. Safe to merge.

Well @bstefanuk actually it was impactful as it led to serious performance degradations in the resulting build, thus we hoped for an explanation. It must be some side effect bug.

@stellaraccident
Copy link
Contributor

--no-enumerate is not an impactful flag, this shouldn't affect the build. Safe to merge.

Well @bstefanuk actually it was impactful as it led to serious performance degradations in the resulting build, thus we hoped for an explanation. It must be some side effect bug.

This and the other comments about --no-enumerate sound serious. Is there some additional root causing needed here?

Comment on lines -218 to -219
# We do not need to do device enumeration at library build time.
set(Options ${Options} "--no-enumerate")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As the comment says, there should be no need to enumerate devices at build time. Removing this line broke Windows builds in TheRock (ROCm/TheRock#1195 (comment)), where we don't yet build hipInfo.exe (ROCm/TheRock#600).

More root cause analysis is needed for this "reported performance regression". What actually changed, and why did removing this flag help? For benchmarks, are the libraries built on the same machines they are being run on? That could explain them expecting to be built with specific options, instead of using a more robust method of enumerating devices at test/benchmark time (on a test machine that might not be the same as the build machine).

TorreZuk pushed a commit that referenced this pull request Aug 7, 2025
SWDEV-531400 - Remove File reorganization backward computability (rocSOLVER)
lamikr pushed a commit that referenced this pull request Aug 19, 2025
This reverts commit 68a380c.

This breaks building rocBLAS on Windows.
HPC-Ken pushed a commit to HPC-Ken/rocm-libraries that referenced this pull request Aug 22, 2025
This reverts commit 68a380c.

This breaks building rocBLAS on Windows.
@stellaraccident
Copy link
Contributor

… (#207)"

This reverts a line in the commit b5b297e --no-enumerate, because of reported performance regression from the staging team.

Let's please revert this patch. The root cause makes no sense and the lack of any reproduction information makes it just lore that we will carry forward indefinitely (and if true, could be hiding a serious problem).

marbre added a commit that referenced this pull request Sep 11, 2025
scottt pushed a commit to scottt/rocm-libraries that referenced this pull request Sep 16, 2025
This reverts commit 68a380c.

This breaks building rocBLAS on Windows.
ammallya pushed a commit that referenced this pull request Sep 18, 2025
SWDEV-531400 - Remove File reorganization backward computability (rocSOLVER)

[ROCm/rocSOLVER commit: 7d3e50c]
stellaraccident pushed a commit that referenced this pull request Oct 3, 2025
This reverts commit 68a380c.

This breaks building rocBLAS on Windows.
SamuelReeder pushed a commit that referenced this pull request Oct 15, 2025
This reverts commit 68a380c.

This breaks building rocBLAS on Windows.
ScottTodd pushed a commit to ScottTodd/rocm-libraries that referenced this pull request Nov 3, 2025
This reverts commit 68a380c.

This breaks building rocBLAS on Windows.
mousdahl-amd pushed a commit that referenced this pull request Nov 6, 2025
This reverts commit 68a380c.

This breaks building rocBLAS on Windows.
ScottTodd pushed a commit to ScottTodd/rocm-libraries that referenced this pull request Nov 7, 2025
This reverts commit 68a380c.

This breaks building rocBLAS on Windows.
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.

9 participants