-
Notifications
You must be signed in to change notification settings - Fork 15
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
contraction errors when using C8 types on AMD gpus #22
Comments
on frontier, using rocm 5.7 (5.6 should be the same), the sample code appears to work properly :
using rocm 5.1.0, the execution goes to the end but norm1 does not match the reference value:
which is also the case for rocm 5.4.3:
i've observed that for rocm below 5.6 there's an issue with the optimization levels beyond -O1 with hipcc that can result in runtime errors such as
when running test_talsh.x so coming back to rocm 5.1.0 but reducing the optimization to -O1 for hipcc results in a norm1 that matches the reference :
so my impression from all of this is that the issue looks to be due to rocm rather than in tal-sh, and that it could be interesting to list rocm 5.6 as a minimum requirement (and/or indicating the decrease in optimization level for earlier rocm versions). |
I have looked at this again, and as it turns out rocm 5.6.0 still shows the issue with yielding an incorrect Norm1 values unless -O1 is used. code compiled with BUILD_TYPE=PRF: -O3
-O2
-O1
with that, i would amend the suggestion to indicate rocm 5.6 still requires the workaround, and rocm 5.7.0 as minimum requirement without it. |
I see error messages when contracting tensors that are of type
complex double (C8)
on AMD GPUs.I consistently see this error with rocm versions
4.5.0
,4.5.2
and5.1.0
.Below is a slimmer version of
test.cpp
which only runs thetest_talsh_c
routine. Additionally changed theR8
occurrences toC8
to reproduce the error. It looks like call to gpu_tensor_block_contract_dlf is where things go wrong. This call returns a task error code that is > 0 for when the tensor type isC8
.The text was updated successfully, but these errors were encountered: