- 06 Dec, 2018 1 commit
-
-
Robert Maynard authored
-
- 23 Oct, 2018 1 commit
-
-
Robert Maynard authored
std::containers only activate fast emplace operations if the T types move operators are noexcept
-
- 25 Sep, 2018 1 commit
-
-
Sujin Philip authored
-
- 05 Jun, 2018 1 commit
-
-
Kitware Robot authored
Code extracted from: https://gitlab.kitware.com/third-party/taotuple.git at commit ae4936580baf117373e73c23f0f8407d7589e6ff (for/vtk-m).
-
- 04 Apr, 2018 1 commit
-
-
Robert Maynard authored
Previously memory that was allocated outside of VTK-m was impossible to transfer to VTK-m as we didn't know how to free it. By extending the ArrayHandle constructors to support a Storage object that is being moved, we can clearly express that the ArrayHandle now owns memory it didn't allocate. Here is an example of how this is done: ```cpp T* buffer = new T[100]; auto user_free_function = [](void* ptr) { delete[] static_cast<T*>(ptr); }; vtkm::cont::internal::Storage<T, vtkm::cont::StorageTagBasic> storage(buffer, 100, user_free_function); vtkm::cont::ArrayHandle<T> arrayHandle(std::move(storage)); ```
-
- 16 Feb, 2018 1 commit
-
-
Robert Maynard authored
-
- 27 Oct, 2017 1 commit
-
-
Sujin Philip authored
Fixes #170
-
- 20 Sep, 2017 1 commit
-
-
Kenneth Moreland authored
Sandia National Laboratories recently changed management from the Sandia Corporation to the National Technology & Engineering Solutions of Sandia, LLC (NTESS). The copyright statements need to be updated accordingly.
-
- 07 Aug, 2017 1 commit
-
-
Robert Maynard authored
-
- 26 May, 2017 1 commit
-
-
Robert Maynard authored
clang-format BinPack settings have been disabled to make sure that the VTK-m style guideline is obeyed.
-
- 25 May, 2017 1 commit
-
-
Kitware Robot authored
-
- 08 Mar, 2017 1 commit
-
-
Kenneth Moreland authored
The basic storage has an implicit invariant that if the size of the storage is 0 then the array is a null pointer. That invariant was broken if the array was allocated and then Shrink or Allocate was called with 0. In that case, the array remained allocated by the size was set to 0. This fixes the problem by making sure a Shrink(0) actually does an Allocate(0) (to clear out the data) and that the basic storage always frees its memory when allocating a 0 sized array.
-
- 14 Feb, 2017 2 commits
-
-
Kenneth Moreland authored
Previously if you constructed an array handle without allocating it, you would get an error if you tried to use the array as input. This conflicted with some recent changes to accept empty vectors. Now when you try to use an unallocated ArrayHandle as input (calling PrepareForInput or PrepareForInPlace), it internally calls Allocate(0) (to establish internal state) and sets up a valid execution ArrayPortal of size 0.
-
Robert Maynard authored
-
- 07 Feb, 2017 1 commit
-
-
David C. Lonie authored
Remove the ErrorControl class such that all subclasses now inherit from error. Renamed all exception classes via s/ErrorControl/Error/. See issue #57.
-
- 16 Jan, 2017 1 commit
-
-
Robert Maynard authored
To help reduce compile and library size the vtkm_cont library now holds common instantiations.
-