mirror of
https://gitlab.kitware.com/vtk/vtk-m
synced 2024-09-16 17:22:55 +00:00
0797359c57
With recent changes to `Arrayhandle`, the type for the associated array portal is now the same across all devices. This means that almost all exec objects no longer need to be specialized on the device types. Thus, clean up the whole array exec objects to no longer need to be templated on device.
86 lines
2.9 KiB
C++
86 lines
2.9 KiB
C++
//============================================================================
|
|
// Copyright (c) Kitware, Inc.
|
|
// All rights reserved.
|
|
// See LICENSE.txt for details.
|
|
//
|
|
// This software is distributed WITHOUT ANY WARRANTY; without even
|
|
// the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
|
|
// PURPOSE. See the above copyright notice for more information.
|
|
//============================================================================
|
|
#ifndef vtk_m_cont_arg_TransportTagWholeArrayInOut_h
|
|
#define vtk_m_cont_arg_TransportTagWholeArrayInOut_h
|
|
|
|
#include <vtkm/Types.h>
|
|
|
|
#include <vtkm/cont/ArrayHandle.h>
|
|
|
|
#include <vtkm/cont/arg/Transport.h>
|
|
|
|
#include <vtkm/exec/ExecutionWholeArray.h>
|
|
|
|
namespace vtkm
|
|
{
|
|
namespace cont
|
|
{
|
|
namespace arg
|
|
{
|
|
|
|
/// \brief \c Transport tag for in-place arrays with random access.
|
|
///
|
|
/// \c TransportTagWholeArrayInOut is a tag used with the \c Transport class to
|
|
/// transport \c ArrayHandle objects for data that is both input and output
|
|
/// (that is, in place modification of array data).
|
|
///
|
|
/// The worklet will have random access to the array through a portal
|
|
/// interface, but care should be taken to not write a value in one instance
|
|
/// that will be read by or overridden by another entry.
|
|
///
|
|
struct TransportTagWholeArrayInOut
|
|
{
|
|
};
|
|
|
|
template <typename ContObjectType, typename Device>
|
|
struct Transport<vtkm::cont::arg::TransportTagWholeArrayInOut, ContObjectType, Device>
|
|
{
|
|
// MSVC will issue deprecation warnings here if this template is instantiated with
|
|
// a deprecated class even if the template is used from a section of code where
|
|
// deprecation warnings are suppressed. This is annoying behavior since this template
|
|
// has no control over what class it is used with. To get around it, we have to
|
|
// suppress all deprecation warnings here.
|
|
#ifdef VTKM_MSVC
|
|
VTKM_DEPRECATED_SUPPRESS_BEGIN
|
|
#endif
|
|
|
|
// If you get a compile error here, it means you tried to use an object that
|
|
// is not an array handle as an argument that is expected to be one.
|
|
VTKM_IS_ARRAY_HANDLE(ContObjectType);
|
|
|
|
using ValueType = typename ContObjectType::ValueType;
|
|
using StorageTag = typename ContObjectType::StorageTag;
|
|
|
|
using ExecObjectType = vtkm::exec::ExecutionWholeArray<ValueType, StorageTag>;
|
|
|
|
template <typename InputDomainType>
|
|
VTKM_CONT ExecObjectType operator()(ContObjectType& array,
|
|
const InputDomainType&,
|
|
vtkm::Id,
|
|
vtkm::Id,
|
|
vtkm::cont::Token& token) const
|
|
{
|
|
// Note: we ignore the size of the domain because the randomly accessed
|
|
// array might not have the same size depending on how the user is using
|
|
// the array.
|
|
|
|
return ExecObjectType(array, Device{}, token);
|
|
}
|
|
|
|
#ifdef VTKM_MSVC
|
|
VTKM_DEPRECATED_SUPPRESS_END
|
|
#endif
|
|
};
|
|
}
|
|
}
|
|
} // namespace vtkm::cont::arg
|
|
|
|
#endif //vtk_m_cont_arg_TransportTagWholeArrayInOut_h
|