Closed maddyscientist closed 1 year ago
@griwes thoughts
I took a quick look. There's a very special function at this line of code, some kind of compact between libcxx and ASAN, and it has one of the macros we modified applied to it. I bet that if we just unapplied our modified macro from it (after all, it's not a GPU function) then it would either pass or find the next error.
This has been fixed by https://github.com/NVIDIA/libcudacxx/pull/206 AFAIK so closing
In testing libcu++ for deployment in QUDA, I found that libcu++ atomic fails to compile if address sanitizer is enabled.
Where bug.cu is simply the following
I note that this is blocking us from deploying libcu++ for production in QUDA, and forcing us to keep around legacy our legacy
atomicAdd
-based andcudaStream
approach to reductions.Tested on the latest release 1.4.1.