1. 21 May, 2015 1 commit
  2. 17 May, 2015 1 commit
  3. 14 May, 2015 4 commits
  4. 13 May, 2015 1 commit
  5. 08 May, 2015 3 commits
  6. 07 May, 2015 3 commits
    • Kenneth Moreland's avatar
      Fix issues with warnings about data loss from type conversion · 66aa10aa
      Kenneth Moreland authored
      Fix compile warnings that come up with the flags
        -Wconversion -Wno-sign-conversion
      This catches several instances (mostly in the testing framework) where
      types are implicitly converted. I expect these changes to fix some of
      the warnings we are seeing in MSVC.
      I was going to add these flags to the list of extra warning flags, but
      unfortunately the Thrust library has several warnings of these types,
      and I don't know a good way to turn on the warnings for our code but
      turn them off for Thrust.
    • Kenneth Moreland's avatar
      Compare with tolerance in UnitTestArrayHandlePermutation · 229579c3
      Kenneth Moreland authored
      The UnitTestArrayHandlePermutation test was failing when compiled with
      icc. I believe the issue is that the icc optimization takes some
      liberties when computing literal floating point values versus computing
      them at run time that makes the two slightly different. I changed all
      the applicable comparisons in this test from using the == operator to
      using the test_equal function, which adds a tolerance to the comparison.
      I expect this to fix the test failure.
    • Kenneth Moreland's avatar
      Make VTKM_ASSERT_CONT gracefully ignore CUDA devices · c9f6628c
      Kenneth Moreland authored
      There are often instances where one wants to make an assert check in a
      method that can run in either the control or execution environment. This
      is rather difficult in general for the execution environment, but with
      this change you can place the VTKM_ASSERT_CONT macro in such a method,
      and it should compile even under CUDA. It works by removing the macro if
      compiling for a CUDA device.
  7. 06 May, 2015 2 commits
  8. 05 May, 2015 3 commits
  9. 04 May, 2015 3 commits
  10. 01 May, 2015 1 commit
  11. 30 Apr, 2015 2 commits
    • Kenneth Moreland's avatar
      Change storage references to storage pointers. · e14fc427
      Kenneth Moreland authored
      Previously ArrayTransfer and ArrayManagerExecution received a reference
      to a Storage class in their constructor and held the reference as an
      ivar. In retrospect, this is just asking for trouble. First, it is way
      too easy to pass by value when you mean to pass by reference. Second, if
      there ever is a bug where the Storage goes out of scope before the
      classes holding a reference, it is that much harder to debug.
    • Kenneth Moreland's avatar
      Change interface of ArrayTransfer to be more like ArrayHandle. · ec0adf8b
      Kenneth Moreland authored
      This includes changing methods like LoadDataForInput to PrepareForInput.
      It also changed the interface a bit to save a reference to the storage
      object. (Maybe it would be better to save a pointer?) These changes also
      extend up to the ArrayManagerExecution class, so it can effect device
      adapter implementations.
  12. 28 Apr, 2015 2 commits
    • Kenneth Moreland's avatar
      Remove LoadDataForInput that takes portals. · c5b831b7
      Kenneth Moreland authored
      This API change effects both ArrayTransfer and ArrayManagerExecution.
      This is in preparation for a future change to make the API more
      consistent with ArrayHandle.
    • 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.
  13. 23 Apr, 2015 4 commits
  14. 16 Apr, 2015 2 commits
  15. 13 Apr, 2015 2 commits
  16. 08 Apr, 2015 1 commit
  17. 03 Apr, 2015 1 commit
  18. 23 Mar, 2015 1 commit
  19. 10 Mar, 2015 1 commit
    • Robert Maynard's avatar
      Move back to thrust::cuda::vector to properly handle allocating uint8's · 86dc8f1d
      Robert Maynard authored
      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.
  20. 09 Mar, 2015 1 commit
  21. 05 Mar, 2015 1 commit