HIP/GCC host-only warning#5428
Closed
wiersema1 wants to merge 1 commit intoAMReX-Codes:developmentfrom
Closed
Conversation
….H were complaining about being host-only. Added device-side operators.
Member
|
Could you tell me how to reproduce the issue with ERF? ERF does have a HIP CI that does not have the issue. |
Member
|
It might also help if you can compile with |
Member
|
I could not reproduce it on frontier. |
Author
|
@WeiqunZhang I found the issue and it was entirely on my end. In my build script I had the GCC C++ headers provided via CPLUS_INCLUDE_PATH rather than in the cmake CXX_FLAGS, which meant GCC's was prioritized over the ROCm . Thank you for your time and sorry to raise a non-issue! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
For HIP/GCC builds, the new/delete operators in Src/Base/AMReX_BaseFab.H gave me host-only warnings. This PR adds device-side operator overloads to resolve the issue.
I'd welcome a careful review of these changes to catch any unintended side effects since I'm not comfortably familiar with AMReX internals.
Additional background
The following is from compiling the ERF model.
My build environment includes
Checklist
The proposed changes: