Robert Maynard 86dc8f1d38 Move back to thrust::cuda::vector to properly handle allocating uint8's ... Our approach of using the underlying allocator inside thrust was a bad approach, for some reason it fails to properly allocate uint8's or int8's on the correct boundaries. I expect that this logic is somewhere else in the code and instead we should use thrust::system::cuda::vector which does this properly.		2015-03-10 10:10:03 -04:00
..
testing	Adding a cuda device adapter to vtkm.	2014-12-19 13:47:28 -05:00
ArrayManagerExecutionCuda.h	Adding a cuda device adapter to vtkm.	2014-12-19 13:47:28 -05:00
ArrayManagerExecutionThrustDevice.h	Move back to thrust::cuda::vector to properly handle allocating uint8's	2015-03-10 10:10:03 -04:00
CMakeLists.txt	Adding a cuda device adapter to vtkm.	2014-12-19 13:47:28 -05:00
DeviceAdapterAlgorithmCuda.h	Adding a cuda device adapter to vtkm.	2014-12-19 13:47:28 -05:00
DeviceAdapterAlgorithmThrust.h	Add in initial support for texture binding of input arrays.	2014-12-19 13:47:28 -05:00
DeviceAdapterTagCuda.h	Adding a cuda device adapter to vtkm.	2014-12-19 13:47:28 -05:00
MakeThrustIterator.h	Simplify the implementation of loading through textures.	2015-03-09 16:37:45 -04:00
SetThrustForCuda.h	Adding a cuda device adapter to vtkm.	2014-12-19 13:47:28 -05:00