-
Notifications
You must be signed in to change notification settings - Fork 129
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
Segmentation fault in SPMV benchmark on GPU target #1269
Comments
The problem seems to be caused by the fact that array
It looks like all access nodes get GPU_Global allocation by default, no matter how they are used in the generated code:
|
I have skipped the
The reason is that the parallel optimisation converts the outer |
We are going to start working on this. #1291 has a quick fix for the specific benchmark if you want to test it. |
I have tested it on GPU and it works. Thanks |
However, I see now that the
Here is the full exception from the transformation:
|
This is a workflow/ordering of transformations-related issue. We have introduced a workaround in the branch |
The issue is finally being fixed by utilizing the auto-optimizer's new |
Thank you. I have also tested it and it works. |
Segmentation fault when running the
spmv
benchmark from npbench withdace_gpu
frameworkFrom gdb backtrace it is possible to locate the segmentation in access to
A_row
array:and visualize some context:
The generated code looks like:
The environment looks like:
The text was updated successfully, but these errors were encountered: