Skip to content

Conversation

@davidbeckingsale
Copy link
Member

Inspired by #596 , but doesn't support hipcc

Copy link
Member

@adayton1 adayton1 left a comment

Choose a reason for hiding this comment

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

Thanks, David!


# AMDGPU_TARGETS should be defined in the hip-config.cmake that gets "included" via find_package(hip)
# This file is also what hardcodes the --offload-arch flags we're removing here
if(DEFINED AMDGPU_TARGETS)
Copy link
Member

Choose a reason for hiding this comment

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

It seems like there's no longer a point for having AMDGPU_TARGETS.

Copy link
Member

@adayton1 adayton1 Feb 4, 2025

Choose a reason for hiding this comment

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

Or is it used internally by hip's CMake setup?

Copy link
Member

Choose a reason for hiding this comment

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

I don't see it in CMake's source, maybe it is in the FindRocm source. I would have expected this to only be used as a backwards compatiblity and maybe just set the CMake variable.

Copy link
Member Author

Choose a reason for hiding this comment

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

I could do backwards compatibility but I think removal might be best since we are going to be having breaking BLT changes soon

Copy link
Member

Choose a reason for hiding this comment

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

i am okay with that as well.

@davidbeckingsale davidbeckingsale merged commit 3c95aa1 into develop Mar 10, 2025
8 checks passed
@white238 white238 deleted the feature/enable_language_hip branch March 10, 2025 21:25
endif()

blt_import_library(NAME blt_hip
COMPILE_FLAGS ${_blt_hip_compile_flags}
Copy link
Member

Choose a reason for hiding this comment

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

I just noticed this: _blt_hip_compile_flags is still set above but it is now unused. Is the fix for --rocm-path with crayftn no longer needed? @davidbeckingsale @white238

Copy link
Member

Choose a reason for hiding this comment

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

@LLNL/blt my question still stands. We've noticed --rocm-path has disappeared from our compile lines.

Copy link
Member Author

@davidbeckingsale davidbeckingsale Apr 30, 2025

Choose a reason for hiding this comment

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

If something is being compiled as LANGUAGE HIP then why would you need the rocm-path to be manually added (or for it to be guarded from CrayFTN)?

Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure, but something about the BLT update now causes some run time failures for us. We're experimenting to try to narrow it down. Adding --rocm-path back in doesn't fix it for us, but if it's really not needed, then all the code to set _blt_hip_compile_flags should be removed.

Copy link
Member

@adayton1 adayton1 May 2, 2025

Choose a reason for hiding this comment

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

Looks like it is not --rocm-path that was the issue. We had a dependency that was ignoring the BLT we were telling it to use and instead using its own internal BLT. We switched from using AMDGPU_TARGETS to CMAKE_HIP_ARCHITECTURES when we migrated to BLT v0.7.0, but the old BLT was still relying on AMDGPU_TARGETS. So the code to set _blt_hip_compile_flags should probably be removed.

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.

5 participants