GitLab

3dda0ab2 Correct unused-parameter warnings from defaulted methods.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1663

GCC 6 warns about defaulted methods when parameters have names.

27426b7b Fix warnings found with clang-8 inside the OpenMP device adapter.
cec9af64 Update the lsan suppression to capture tbb leaks.
8ef2c4be TransferInfo doesn't leak when holding VirtualObjectTransferShareWithControl
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1661

d468784f Correct more host/device warnings from methods that should be host only
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1660

Additionally document that we only want to suppress the known
leak in loguru::set_thread_name.

When TransferInfo is given memory from VirtualObjectTransferShareWithControl
it doesn't have a bound function ptr for the destruction. In those cases
we need to make sure the HostCopyOfDevice is properly deleted, otherwise
we will cause a memory leak.

bdabfbe1 Make sure ArrayPortalUniformPointCoordinates constructor is explicit
b3d951b5 vtkm::Range Include function now requires half as many min/max calls
ddaa0df2 ArrayHandleVirtualCoordinates now calls the proper parent constructor
61e80037 Make sure all execution side CellLocator objects have explicit destructors
307898ff Cleanup the CellLocatorBoundingIntervalHierarchy.cxx style.
0f31c69f Remove unnecessary constructor from ParameterContainer
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1657

967581cf Merge branch 'upstream-taotuple' into update_tao_cuda_pragmas
90784608 taotuple 2019-04-24 (57001975)
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1659

* upstream-taotuple:
  taotuple 2019-04-24 (57001975)

Code extracted from:

    https://gitlab.kitware.com/third-party/taotuple.git

at commit 5700197521301b5dd102f81d0073f83e15e5a7e5 (for/vtk-m).

We have had problems in the past with host/device default constructors

Previously it was calling the ArrayHandle<T,StorageTagVirtual>
constructor and not the ArrayHandleVirtual constructor which
generated a warning with some compilers

ee2999d1 Some classes should be exported
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Robert Maynard <robert.maynard@kitware.com>
Merge-request: !1656

63c931e6 Correct location of ThrustPatches which clang formatter moved
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1653

6fafcf01 correct compile issues caused by clang formatting.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1655

A couple of tests require vtkm/testing/Testing to be the first include

90dd8a0e Correct clang formatting in Math.h.in
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Robert Maynard <robert.maynard@kitware.com>
Merge-request: !1654

There is a small section in the code generated from Math.h.in that is
subject to clang formatting. A recent change reformatted that bit of
Math.h, so we need to update Math.h.in accordingly.

ff687016 For VTK-m libs all includes of DeviceAdapterTagCuda happen from cuda files
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1648

030b03e4 Remove unneeded diy build include directory
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1652

The diy build configured files are all located by the include
from the root vtkm include directory, so this include isn't needed

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.

13ef17ea Remove thread_local from RuntimeDeviceNames
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1650

Older Mac compilers that are still supported by VTK don't support
`thread_local`.

d8cc067c Remove DeviceAdapterError as it isn't needed any more.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1649

Fixes #277

DeviceAdapterError existed to make sure that the default device adapter
template was being handled properly. Since the default device adapter doesn't
exist, and nothing is templated over it we can now remove DeviceAdapterError.

21c84798 FieldIn/Out/InOut documentation updated to fact they aren't templated
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !1647

Fixes #366

5a26051f benchmarking cmake code simplified
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1646

9c292007 UnitTestBoundingIntervalHierarchy handles systems under load better
671c1df5 Timer logs the proper device name when called with an invalid device
d3d66a33 GameOfLife example always uses the proper device adapter
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1645

The UnitTestBoundingIntervalHierarchy has historically had problems
when the machine is already under-load when the algorithm is executed.
By limiting the number of openMP threads the test uses we can
reduce the amount of CPU time slicing that this test causes.