1. 21 May, 2015 1 commit
  2. 28 Apr, 2015 1 commit
    • Kenneth Moreland's avatar
      Remove UserPortal from ArrayHandle. · a2c28099
      Kenneth Moreland authored
      The UserPortal in ArrayHandle was used to copy a pointer the user
      created into an ArrayHandle to use in VTK-m algorithms. However, this is
      only really valid for a basic storage, so the functionality has been
      moved there, and you have to construct an ArrayHandle with a storage
      instead of an array portal.
      a2c28099
  3. 23 Oct, 2014 1 commit
    • Kenneth Moreland's avatar
      delete operator and std::allocator are not necessarily the same · bc3e1ebd
      Kenneth Moreland authored
      The unit test for StorageBasic tested the StealArray feature and then
      used the delete[] operator on the stolen array to deallocate it. For
      many standard libraries the default implementation for delete[] is
      the same as (or at least compatible with) std::allocator, but for
      the PGI compiler they were not compatible and this resulted in a
      run-time error. This change fixes the problem with the test by using
      the same allocator as the StorageBasic test.
      bc3e1ebd
  4. 24 Jun, 2014 1 commit
    • Kenneth Moreland's avatar
      Change ArrayContainerControl to Storage. · 21823500
      Kenneth Moreland authored
      After a talk with Robert Maynard, we decided to change the name
      ArrayContainerControl to Storage. There are several reasons for this
      change.
      
      1. The name ArrayContainerControl is unwieldy. It is long, hard for
      humans to parse, and makes for long lines and wraparound. It is also
      hard to distinguish from other names like ArrayHandleFoo and
      ArrayExecutionManager.
      
      2. The word container is getting overloaded. For example, there is a
      SimplePolymorphicContainer. Container is being used for an object that
      literally acts like a container for data. This class really manages
      data.
      
      3. The data does not necessarily have to be on the control side.
      Implicit containers store the data nowhere. Derivative containers might
      have all the real data on the execution side. It is possible in the
      future to have storage on the execution environment instead of the
      control (think interfacing with a simulator on the GPU).
      
      Storage is not a perfect word (what does implicit storage really mean?),
      but its the best English word we came up with.
      21823500
  5. 11 Jun, 2014 1 commit
  6. 07 Mar, 2014 1 commit
  7. 11 Feb, 2014 1 commit
  8. 10 Feb, 2014 1 commit