1. 10 Jul, 2018 1 commit
  2. 09 Jul, 2018 4 commits
  3. 06 Jul, 2018 3 commits
    • Robert Maynard's avatar
      Merge topic 'support_pointers_as_input_to_dispatcher_invoke' · 1e28a9e3
      Robert Maynard authored
      64958b01 VTK-m now supports passing pointers when invoking worklets.
      c631dccf Invocation parameters are now non const and can be 'modified'
      Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
      Acked-by: Kenneth Moreland's avatarKenneth Moreland <kmorel@sandia.gov>
      Merge-request: !1303
      1e28a9e3
    • Robert Maynard's avatar
      VTK-m now supports passing pointers when invoking worklets. · 64958b01
      Robert Maynard authored
      The original design of invoke and the transport infrastructure
      relied on the implementation behavior of vtkm::cont types
      such as ArrayHandle that used an internal shared_ptr to managed
      state. This allowed passing by value instead of passing by
      non-const ref when needing to transfer information to the device.
      
      As VTK-m adds support for classes that use virtuals the ability
      to pass by base pointer type allows for us to invoke worklets
      using a base type without the risk of type slicing.
      
      Additional by moving over to a non-const ref Invocation we
      can update all transports that have 'output' to now be
      by ref and therefore support types that can't be copied while
      being 'more' correct.
      64958b01
    • Robert Maynard's avatar
      Invocation parameters are now non const and can be 'modified' · c631dccf
      Robert Maynard authored
      The invocation parameters need to be non const as we want to
      be able to call non-const methods like `PrepareForOutput` on them
      from a transport function.
      
      The original implementation abused the fact that everything
      could be copied by value and have that work properly. But
      when we start introducing virtual classes copying by value of
      a base type can cause type slicing.
      c631dccf
  4. 05 Jul, 2018 6 commits
  5. 03 Jul, 2018 5 commits
  6. 02 Jul, 2018 7 commits
  7. 01 Jul, 2018 1 commit
  8. 30 Jun, 2018 4 commits
  9. 29 Jun, 2018 9 commits