diff options
author | Rohit Santhanam <rohit.santhanam@amd.com> | 2021-04-08 15:14:48 +0000 |
---|---|---|
committer | Rohit Santhanam <rohit.santhanam@amd.com> | 2021-04-08 15:14:48 +0000 |
commit | 2859db0220cd8644c1a75a3bf04f62f551f73f22 (patch) | |
tree | f56474975bde98d84cb0aaba059872b4c281a9c1 /bench/perf_monitoring/gemv_settings.txt | |
parent | fcb5106c6e16599eeabadf7d82a465d52229698f (diff) |
This fixes an issue where the compiler was not choosing the GPU specific specialization of ScanLauncher.
The issue was discovered when the GPU scan unit test was run and resulted in a segmentation fault.
The segmantation fault occurred because the unit test allocated GPU memory and passed a pointer to that memory to the computation that it presumed would execute on the GPU.
But because of the issue, the computation was scheduled to execute on the CPU so a situation was constructed where the CPU attempted to access a GPU memory location.
The fix expands the GPU specific ScanLauncher specialization to handle cases where vectorization is enabled.
Previously, the GPU specialization is chosen only if Vectorization is not used.
Diffstat (limited to 'bench/perf_monitoring/gemv_settings.txt')
0 files changed, 0 insertions, 0 deletions