rocm-systems

hipArray.cpp

2017-03-15 12:03:44 +05:30

hipHostGetFlags.cpp

Revert "Revert adoption of CUDA indexing in general - this can only work with later versions of the compiler, just like module based dispatch, and thus must be guarded against usage in earlier (e.g. 1.6) versions."

2017-11-29 21:49:10 +00:00

hipHostMalloc.cpp

Revert "Revert adoption of CUDA indexing in general - this can only work with later versions of the compiler, just like module based dispatch, and thus must be guarded against usage in earlier (e.g. 1.6) versions."

2017-11-29 21:49:10 +00:00

hipHostRegister.cpp

Revert "Revert adoption of CUDA indexing in general - this can only work with later versions of the compiler, just like module based dispatch, and thus must be guarded against usage in earlier (e.g. 1.6) versions."

2017-11-29 21:49:10 +00:00

hipMemcpy_simple.cpp

This switches HIP from its currently convoluted macro + pfe based dispatch mechanism to a more natural one partially based on the existing module API. The basic idea is that HCC will always correctly emit __global__ functions: as empty-bodied stubs, on host, and as kernels, on device. It then becomes trivial to obtain the mangled name on host, at dispatch, from the function's address, and then to use the mangled name to retrieve the kernel. This should address all problems stemming from serialisation, dubious mismatches due to the manufactured functor, macro-isms et al. It also immediately enables support for generalised globals as a consequence of that being available in the module API. Finally, it will make debug much easier, since the actual names of the __global__ functions will automatically be used in traces etc. One detail is that due to how dispatch works now (hipLaunchKernel and hipLaunchKernelGGL are themselves variadic function templates which deduce the function type of the callee), in certain cases it may be necesssary to insert explicit casts to ensure that the variadic argument list selects a viable overload - this can be observed in some unit tests. Eventually we may be able to remove this limitation, but for now it does not appear terribly onerous. The code is not extremely HIPpie, nor is it fully optimised, but rather is intended as a starting point for the HIP team to make its own.

2017-11-01 15:09:59 +00:00

hipMemcpy.cpp

[nvccWarnings] Fix warnings seen with dtests on nvcc path

2017-12-14 14:10:37 +05:30

hipMemcpyAll.cpp

directed tests: Updated to use new hip include path

2016-10-04 22:20:50 +05:30

hipMemcpyAsync2.cpp

changed __global__ attribute

2017-02-03 10:53:36 -06:00

hipMemcpyAsync.cpp

Revert "Revert adoption of CUDA indexing in general - this can only work with later versions of the compiler, just like module based dispatch, and thus must be guarded against usage in earlier (e.g. 1.6) versions."

2017-11-29 21:49:10 +00:00

hipMemcpyDtoD.cpp

Update new tests so as to make them work with new variadic based launch mechanisms.

2017-11-10 00:14:34 +00:00

hipMemcpyDtoDAsync.cpp

Update new tests so as to make them work with new variadic based launch mechanisms.

2017-11-10 00:14:34 +00:00

hipMemcpyPeer.cpp

[nvccWarnings] Fix warnings seen with dtests on nvcc path

2017-12-14 14:10:37 +05:30

hipMemcpyPeerAsync.cpp

Re-sync with upstream.

2017-11-20 15:34:50 +00:00

hipMemoryAllocateCoherent.cpp

Revert "Revert adoption of CUDA indexing in general - this can only work with later versions of the compiler, just like module based dispatch, and thus must be guarded against usage in earlier (e.g. 1.6) versions."

2017-11-29 21:49:10 +00:00

hipMemoryAllocateCoherentDriver.cpp

Add direct test case for threadfence_system workaround

2016-11-11 15:09:43 -06:00

hipMemPtrGetInfo.cpp

Disable hipMemPtrGetInfo test on nvcc path

2017-03-08 16:16:08 +05:30

hipMemset.cpp

directed tests: Updated to use new hip include path

2016-10-04 22:20:50 +05:30

hipRandomMemcpyAsync.cpp

changed __global__ attribute

2017-02-03 10:53:36 -06:00

hipTestMemcpyPin.cpp

changed __global__ attribute

2017-02-03 10:53:36 -06:00

p2p_copy_coherency.cpp

[nvccWarnings] Fix warnings seen with dtests on nvcc path

2017-12-14 14:10:37 +05:30