Peter Heywood

> Unified Memory has two basic requirements: > > + a GPU with SM architecture 3.0 or higher (Kepler class or newer) > > + a 64-bit host application and...

using CCCL with 11.0 is DOA: > For instance, CCCL requires a minimum supported version of 11.1 from the 11.x series due to an unavoidable compiler issue present in CTK...

> > so we can just rely on 11.2 +'s stability promises > > This seems like the best plan, assuming you're not aware of any HPC with only super...

During meeting concluded that dropping CUDA 11.0 support in favour of future CCCL support is worthwhile / CUDA 11.2 is old enough to be a minimum. I'll adjust CI to...

Looks like the previous windows cuda 11.0 CI errors were actually a github actions windows-2019 vs windows-2022 difference. i.e. visual studio 2019 issue? ``` 2023-12-01T16:10:13.7088440Z ##[error] 1>D:\a\FLAMEGPU2\FLAMEGPU2\build\_deps\cccl-src\libcudacxx\include\cuda\std\detail\libcxx\include\__type_traits/is_constant_evaluated.h(27): error : identifier...

It's still supported by CUDA, which libcucxx/CCCL claim to support the same platforms as so afiak it should work / be supported. I had a quick look into the error...

I do have visual studio 2019 installed, but only cuda 11.7 and 12.0 on windows currently. Can select the cuda toolkit via `-T` from the command line, i.e. using 11.7...

11.2 + visual studio 2019 has reproduced the error locally. A quick attempt to configure cccl standalone failed as I'm missing a test suite dependency.

Reproduced the error using the CCCL example locally with visual studio 2019. ``` git clone [email protected]:nvidia/CCCL cd CCCL/examples/example_project mkdir build cd build cmake cmake .. -A x64 -G "Visual Studio...

CUDA 12.3 vs 2022 tests pass. CI sweep pinning down vs2019 + CUDA 11.x versions which exhibit the libcu++ compilation error, will report upstream tomorrow once versions are known. 11.7...