This repository was archived by the owner on Jan 26, 2024. It is now read-only.
amd_detail: fix atomicMax and atomicMin for floating point types#40
Open
psychocoderHPC wants to merge 1 commit intoROCm:developfrom
Open
amd_detail: fix atomicMax and atomicMin for floating point types#40psychocoderHPC wants to merge 1 commit intoROCm:developfrom
atomicMax and atomicMin for floating point types#40psychocoderHPC wants to merge 1 commit intoROCm:developfrom
Conversation
The return value of `atomicMax` and `atomicMin` should be the old value from the destination memory. This was not the case before the fix. In cases where no concurrent thread is manipulating the destination the returned values were always the value passed to the atomic function.
|
This issue has been already addressed in an internal version of hipamd. It will eventually make it on this repository as well. |
Author
|
@afanfa I would say that If the data in memory tmp==32 and value==4) the return value is 4 but should be 32. |
Author
|
|
Author
|
|
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The return value of
atomicMaxandatomicMinshould be the old value from the destination memory.This was not the case before the fix.
In cases where no concurrent thread is manipulating the destination the returned values were always the value passed to the atomic function.
test case (for float/double):
output: