Skip to content

remove options --no-enumerate #966

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 1, 2025
Merged

remove options --no-enumerate #966

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e897bd5
Revert "Re-apply Windows compatibility fixes to command construction.…
NaveenElumalaiAMD Jul 30, 2025
4aec3bb
Revert "Revert "Re-apply Windows compatibility fixes to command const…
NaveenElumalaiAMD Jul 31, 2025
f9bb0e7
Remove options --no-enumerate
NaveenElumalaiAMD Jul 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions shared/tensile/Tensile/cmake/TensileConfig.cmake
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -215,9 +215,6 @@ function(TensileCreateLibraryFiles
set(Options ${Options} "--architecture=${archString}")
endif()

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

@ScottTodd ScottTodd Aug 6, 2025

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).


set(CommandLine ${Script} ${Options} ${Tensile_LOGIC_PATH} ${Tensile_OUTPUT_PATH} HIP)
if (WIN32 OR (VIRTUALENV_BIN_DIR AND VIRTUALENV_PYTHON_EXENAME))
set(CommandLine ${VIRTUALENV_BIN_DIR}/${VIRTUALENV_PYTHON_EXENAME} ${CommandLine})
Expand Down