Zahra Khatami

From issue#1785 on thrust (https://github.com/NVIDIA/cccl/issues/818), for this small test case: `#include #include int main() { thrust::device_vector dv; thrust::sort(dv.begin(), dv.end()); }` when compiled with -gpu=cc60 and then run it on a...

@allisonvacanti @jrhemstad The "Reviewers" button is disabled for me for some reason and I cant fix it, so and I am not able to add any reviewers for this change....

Is there any release targeted for NVIDIA/thrust#556? If its unknown, then might be beneficial from user perspective to have this fix with current CUB design. In this proposal, is there...

@jrhemstad @dkolsen-pgi @senior-zero I've moved my changes to thrust instead based on David's suggestion. Here is my pull request: https://github.com/NVIDIA/thrust/pull/1848 Still, I'm not able to add any reviewers here. The...

I'm closing this pull since I've moved the changes to thrust.

These are the stdpar algorithms that are implemented directly through corresponding Thrust algorithms and can serve as an initial list of algorithms for the smoke tests: ``` adjacent_difference, exclusive_scan, inclusive_scan,...

The fix doesn’t seem to be comprehensive enough, as this case still fails: ``` #include #include #include #include #include #include #include int main() { std::mt19937 gen(1729); std::vector s(1729); std::generate(s.begin(), s.end(),...

@bernhardmgruber would you please take a look?

Do we always need to set CUDA-related environment variables, even if the tests are not meant to be compiled for the device? It seems that `CUDA_COMPILER` and `CUDA_HOST_COMPILER` are required...