Kenneth Moreland dad18e1170 Improve 3D scheduling mechanism in DispatcherBase ... Previously, DispatcherBase had an ivar to determine whether to use the numInstances passed on the stack or to use a 3D range held in a different ivar. This change allows either a 1D range or 3D range to be passed on the stack, which I expect to be closer to how we we handle this when 3D ranges are fully supported. This also fixes a bug introduced with commit fdac208acbfa47b613d899a36cefc32a01e8f0a8 where the Use3DSchedule ivar was not set correctly in UnitTestDispatcherBase.		2015-05-05 08:46:23 -06:00
..
cont	Don't try to include vtkm/exec/cuda unless cuda is enabled.	2015-05-05 07:59:44 -04:00
exec	Don't try to include vtkm/exec/cuda unless cuda is enabled.	2015-05-05 07:59:44 -04:00
internal	Move another FunctionInterface manipulation to be exclusively control	2015-01-15 22:42:36 -07:00
testing	Update the documentation to note have references to dax.	2014-12-10 10:37:25 -05:00
worklet	Improve 3D scheduling mechanism in DispatcherBase	2015-05-05 08:46:23 -06:00
CMakeLists.txt	Add ability to zip function interface objects.	2014-10-16 16:31:55 -06:00
Extent.h	Change vtkm::Tuple to vtkm::Vec	2014-10-08 10:09:43 -06:00
ListTag.h	Add a template that tests whether a type is in a list.	2014-10-22 10:35:56 -06:00
Pair.h	Add utility include to Pair.h	2014-10-23 16:34:52 -06:00
TypeListTag.h	Add a template that tests whether a type is in a list.	2014-10-22 10:35:56 -06:00
Types.h	Adding a cuda device adapter to vtkm.	2014-12-19 13:47:28 -05:00
TypeTraits.h	Remove vtkm::Scalar and vtkm::Vector# types	2014-10-09 08:54:56 -06:00
VecTraits.h	Change VectorTraits to VecTraits.	2014-10-08 10:09:43 -06:00