1. 22 Apr, 2019 1 commit
    • Robert Maynard's avatar
      For VTK-m libs all includes of DeviceAdapterTagCuda happen from cuda files · ff687016
      Robert Maynard authored
      It is very easy to cause ODR violations with DeviceAdapterTagCuda.
      If you include that header from a C++ file and a CUDA file inside
      the same program we an ODR violation. The reasons is that the C++
      versions will say the tag is invalid, and the CUDA will say the
      tag is valid.
      
      The solution to this is that any compilation unit that includes
      DeviceAdapterTagCuda from a version of VTK-m that has CUDA enabled
      must be invoked by the cuda compiler.
      ff687016
  2. 17 Apr, 2019 2 commits
  3. 12 Apr, 2019 1 commit
  4. 09 Apr, 2019 1 commit
  5. 04 Apr, 2019 1 commit
    • Kenneth Moreland's avatar
      Support pyexpander using python 3 · 23f0905a
      Kenneth Moreland authored
      When you install pyexpander with pip under python 3, the executable
      script is now named expander3.py instead of expander.py. Support using
      either file.
      23f0905a
  6. 03 Apr, 2019 2 commits
  7. 26 Mar, 2019 4 commits
  8. 06 Mar, 2019 1 commit
  9. 05 Mar, 2019 2 commits
  10. 04 Mar, 2019 1 commit
  11. 01 Mar, 2019 1 commit
  12. 27 Feb, 2019 1 commit
    • Kenneth Moreland's avatar
      Find threads library in external build · e9591621
      Kenneth Moreland authored
      In certain circumstances (currently, when logging is enabled), VTK-m
      libraries depend on the threading library. However, when the VTK-m
      package was included from an external project, it did not automatically
      find the threads package. This change makes the Threads library loaded
      when the VTK-m package is found.
      e9591621
  13. 04 Feb, 2019 2 commits
  14. 29 Jan, 2019 3 commits
  15. 24 Jan, 2019 1 commit
  16. 16 Jan, 2019 1 commit
    • Robert Maynard's avatar
      Remove VTK-m TestBuild infrastructure · 4ec5bae0
      Robert Maynard authored
      The purpose of the TestBuild infrastructure was to confirm that
      VTK-m didn't have any lexical issues when it was a pure header
      only project. As we now move to have more compiled components
      the need for this form of testing is mitigated. Combined
      with the issue of TestBuilds causing MSVC issues, we should
      just remove this infrastructure.
      4ec5bae0
  17. 09 Jan, 2019 1 commit
  18. 27 Dec, 2018 4 commits
  19. 13 Dec, 2018 1 commit
    • Allison Vacanti's avatar
      Add vtkm::cont::Initialize. · cdb1f568
      Allison Vacanti authored
      Also
      - Renamed vtkm::cont::make_DeviceAdapterIdFromName to just overload
        make_DeviceAdapterId.
      - Refactored CMake logic for unit tests
        - Since we're now querying the device tracker for the names, they
          cannot be all caps.
      - Updated usages of InitLogging to use Initialize instead.
      - Added changelog.
      cdb1f568
  20. 06 Dec, 2018 1 commit
  21. 30 Nov, 2018 1 commit
  22. 29 Nov, 2018 1 commit
  23. 27 Nov, 2018 1 commit
  24. 23 Nov, 2018 1 commit
    • Haocheng LIU's avatar
      Merge worklet testing executables into a device dependent shared library · 88596366
      Haocheng LIU authored
      VTK-m has been updated to replace old per device worklet testing executables with a device
      dependent shared library so that it's able to accept a device adapter
      at runtime.
      Meanwhile, it updates the testing infrastructure APIs. vtkm::cont::testing::Run
      function would call ForceDevice when needed and if users need the device
      adapter info at runtime, RunOnDevice function would pass the adapter into the functor.
      
      Optional Parser is bumped from 1.3 to 1.7.
      88596366
  25. 19 Nov, 2018 1 commit
  26. 12 Nov, 2018 1 commit
  27. 16 Oct, 2018 1 commit
  28. 04 Oct, 2018 1 commit