-
Notifications
You must be signed in to change notification settings - Fork 104
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
Clang omp-target cannot select error. #1274
Comments
@trws Does this mean that there are 2 definitions of |
More details here: https://lc.llnl.gov/gitlab/radiuss/RAJA/-/pipelines/175291 |
That looks like somehow it is being implicitly declare targeted, and accessed from the GPU-side code in a way that isn't valid. In a way it means there are two of them, sort-of, sometimes, but I would have expected that to fail, or at least give a diagnostic, much earlier. |
Translating that, I think |
Also, come to think of it, here's a fantastically inscrutable error message for you @jdoerfert. 😄 |
Same underlying reason as in Backends (AMD and NVPTX) do not support all atomic instruction + atomic scope combinations. |
Hi @jdoerfert @trws, I'm trying to figure out where exactly in RAJA this is tripping up. Is there a way to ask clang/llvm for detailed instruction selection output? I've seen very old versions of clang use this set of options |
This happens still with upstream clang? Can you just do -save-temps and attach the .bc file? |
When compiling for OpenMP Target with clang/ibm-13.0.1, there is clang backend error found by @kab163 :
The text was updated successfully, but these errors were encountered: