-
Notifications
You must be signed in to change notification settings - Fork 67
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
memory access fault when linking dynamic lib that uses hipcub #13
Comments
I'll look into it. |
Does the same thing happen with rocPRIM? |
No, does not happen with rocPRIM. |
We identified the problem: for some reasons in said configuration (linking to a dynamic library that uses hipcub if I use hipcub also in the main program) every kernel is run twice by HIP framework. Some kernels are resistant to that, some are not (access errors). We are not sure why it happens only for hipCUB. Right now we are thinking that probably in here should be a break after |
Here are HIP API traces for correct and incorrect (with bug) execution, where we can clearly the difference. |
I guess we should open issue in HIP repo. |
Should be fixed by ROCm/HIP#575. I don't know which ROCm release will include that. |
I am running into a memory access fault when linking to a dynamic library that uses hipcub if I use hipcub also in the main program (that links to the package that uses hipcub).
Please see the following minimal example hipcub_test.tar.gz
Edit: This does not happen when using rocprim or cub instead of hipcub.
The text was updated successfully, but these errors were encountered: