diff options
| author | Pierre Moreau <dev@pmoreau.org> | 2017-02-02 12:58:09 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2017-02-10 18:46:07 (GMT) |
| commit | c0d7bb8368c3d157d1a2758b620fc726355e554d (patch) | |
| tree | 20c1862708d423f6375eb86929c1ba6cc7bccc47 /Help/prop_inst | |
| parent | 21a125cdbff24efa746249a3b8ccc6296c5f0aff (diff) | |
| download | CMake-c0d7bb8368c3d157d1a2758b620fc726355e554d.zip CMake-c0d7bb8368c3d157d1a2758b620fc726355e554d.tar.gz CMake-c0d7bb8368c3d157d1a2758b620fc726355e554d.tar.bz2 | |
Tests/Cuda: Print asynchronous error messages, if any
As kernel launches are asynchronous, a `cudaGetLastError()` right after
the kernel launch might be executed while the kernel is still running.
Synchronizing the device will ensure that all the work is completed
before progressing further on, and allows to catch errors that were
previously missed.
The `cudaGetLastError()` after the `cudaDeviceSynchronize()` is there
to reset the error variable to `cudaSuccess`.
Diffstat (limited to 'Help/prop_inst')
0 files changed, 0 insertions, 0 deletions