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.
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.
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
Work-Around: Segfault in MPI_Init with HIP #4237
Work-Around: Segfault in MPI_Init with HIP #4237
Changes from 2 commits
9f00595
88f8780
fa2f5c4
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason for not using
ABLASTR_ALWAYS_ASSERT_WITH_MESSAGE
here?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes: anything calling into AMReX functions cannot be used (safely) before AMReX is initialized.
amrex::Assert
implements multiple things, not all of them work with an uninitialized AMReX context.For instance, not even
amrex::Print()
works before init, I had to develop a work-around falling back to all-print in pyAMReX: AMReX-Codes/pyamrex#174Raising a standard exception is a clean thing to do here - we init MPI and technically there is no AMReX involved at this point in time yet.