You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got asked by someone what the state of the art way to enable assertions, e.g. to trigger on OOB access on a cuda::std::span is for CCCL. I replied that we cannot do anything for plain nvcc (yet), because we don't know whether the users intends to have a debug or release build. But if CCCL is consumed via CMake, we would look at the CMAKE_BUILD_TYPE and define CCCL_ENABLE_ASSERTIONS. Or are we?
I did not find where CMake would define CCCL_ENABLE_ASSERTIONS when any of the CCCL libraries is imported, so I conclude that we don't enable assertions anywhere. I think we should enable them for CMake Debug builds.
The text was updated successfully, but these errors were encountered:
I got asked by someone what the state of the art way to enable assertions, e.g. to trigger on OOB access on a
cuda::std::span
is for CCCL. I replied that we cannot do anything for plain nvcc (yet), because we don't know whether the users intends to have a debug or release build. But if CCCL is consumed via CMake, we would look at theCMAKE_BUILD_TYPE
and defineCCCL_ENABLE_ASSERTIONS
. Or are we?I did not find where CMake would define
CCCL_ENABLE_ASSERTIONS
when any of the CCCL libraries is imported, so I conclude that we don't enable assertions anywhere. I think we should enable them for CMake Debug builds.The text was updated successfully, but these errors were encountered: