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.
  2. 17 Apr, 2019 1 commit
  3. 09 Apr, 2019 1 commit
  4. 04 Apr, 2019 1 commit
  5. 05 Jun, 2018 1 commit
  6. 20 Sep, 2017 1 commit
    • Kenneth Moreland's avatar
      Update copyright for Sandia · c3a3184d
      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
  7. 16 Dec, 2015 1 commit
    • Robert Maynard's avatar
      Extend vtkm::DeviceAdapterTraits to include a unique numeric identifier. · c70da5fc
      Robert Maynard authored
      Previously each device adapter only had a unique string name. This was
      not the best when it came to developing data structures to track the status
      of a given device at runtime.
      This adds in a unique numeric identifier to each device adapter. This will
      allow classes to easily create bitmasks / lookup tables for the validity of
  8. 18 Sep, 2015 1 commit
  9. 17 Sep, 2015 1 commit
    • Robert Maynard's avatar
      DeviceAdapter Tags now always exist, and contain if the device is valid. · 4d635d64
      Robert Maynard authored
      Previously it was really hard to verify if a device adapter was valid. Since
      you would have to check for the existence of the tag. Now the tag always
      exists, but instead you query the traits of the DeviceAdapter to see if
      it is a valid adapter.
      This makes compiling with multiple backends alot easier.
  10. 21 May, 2015 1 commit
  11. 19 Dec, 2014 1 commit
    • Robert Maynard's avatar
      Adding a cuda device adapter to vtkm. · d9270e40
      Robert Maynard authored
      Porting the dax device adapter over to vtkm. Unlike the dax version, doesn't
      use the thrust::device_vector, but instead uses thrust::system calls so that
      we can support multiple thrust based backends.
      Also this has Texture Memory support for input array handles. Some more work
      will need to be done to ArrayHandle so that everything works when using an
      ArrayHandle inplace with texture memory bindings.
  12. 11 Jun, 2014 1 commit
  13. 07 Mar, 2014 1 commit
  14. 10 Feb, 2014 2 commits