-
- Downloads
Optionally optimize new iterators in debugging builds.
In the past, folks have complained about poor performance in debugging builds. These new iterators are written such that their complexity optimizes out, but there is still a lot of complexity. On debugging builds without optimization, this can really get in the way and start slowing things down. In anticipation of this request, I'm adding a CMake option VTK_ALWAYS_OPTIMIZE_ARRAY_ITERATORS which, as you might guess, will always optimize array iterators on platforms that support selective optimization in debug builds.
Showing
- Common/Core/CMakeLists.txt 11 additions, 2 deletionsCommon/Core/CMakeLists.txt
- Common/Core/vtkAssume.h 7 additions, 0 deletionsCommon/Core/vtkAssume.h
- Common/Core/vtkConfigure.h.in 3 additions, 0 deletionsCommon/Core/vtkConfigure.h.in
- Common/Core/vtkDataArrayAccessor.h 24 additions, 12 deletionsCommon/Core/vtkDataArrayAccessor.h
- Common/Core/vtkDataArrayMeta.h 33 additions, 4 deletionsCommon/Core/vtkDataArrayMeta.h
- Common/Core/vtkDataArrayRange.h 23 additions, 1 deletionCommon/Core/vtkDataArrayRange.h
- Common/Core/vtkDataArrayTupleRange_AOS.h 134 additions, 26 deletionsCommon/Core/vtkDataArrayTupleRange_AOS.h
- Common/Core/vtkDataArrayTupleRange_Generic.h 253 additions, 73 deletionsCommon/Core/vtkDataArrayTupleRange_Generic.h
- Common/Core/vtkDataArrayValueRange_AOS.h 21 additions, 0 deletionsCommon/Core/vtkDataArrayValueRange_AOS.h
- Common/Core/vtkDataArrayValueRange_Generic.h 138 additions, 42 deletionsCommon/Core/vtkDataArrayValueRange_Generic.h
- Common/Core/vtkMeta.h 0 additions, 12 deletionsCommon/Core/vtkMeta.h
- Common/Core/vtkSetGet.h 41 additions, 0 deletionsCommon/Core/vtkSetGet.h
Loading
Please register or sign in to comment