[alpaka] change assert with ALPAKA_ASSERT_OFFLOAD #219
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some Alpaka kernels have the occupancy lower than the Native CUDA implementation (for example
countFromVector
kernel fromHistoContainer
).I found out that the problem was related to the
assert
use in Alpaka. In Native CUDA, the assert is disabled by default, becoming enabled only if the macroGPU_DEBUG
is set (this is not the case in Alpaka). I changed the assert from the Alpaka implementation with the macroALPAKA_ASSERT_OFFLOAD
from the Alpaka library (compatible from Alpaka 0.6.1). This macro enables assert only ifALPAKA_DEBUG_OFFLOAD_ASSUME_HOST
is set. This change increased the occupancy for some kernels in Alpaka.