This website requires JavaScript.
Esplora
Aiuto
Accedi
AI
/
rocm-systems
Segui
2
Vota
0
Forka
0
Hai già fatto il fork di rocm-systems
Codice
Problemi
Pull Request
Actions
Pacchetti
Progetti
Rilasci
Wiki
Attività
Files
f7919a8321f20bb9bda3fa2bd12e7874e7520266
rocm-systems
/
hipamd
/
tests
/
src
/
runtimeApi
/
memory
T
Cronologia
Alex Voicu
f7919a8321
Merge remote-tracking branch 'origin/master' into feature_use_module_based_dispatch_instead_of_pfe
...
# Conflicts: # tests/src/runtimeApi/stream/hipStreamSync2.cpp
2017-11-08 10:26:30 +00:00
..
hipArray.cpp
Disable broken tests on hcc path
2017-03-15 12:03:44 +05:30
hipHostGetFlags.cpp
Added new API, hipMemPtrGetInfo
2017-03-07 13:46:29 -06:00
hipHostMalloc.cpp
Update tests.
2017-06-04 20:18:37 -05:00
hipHostRegister.cpp
Refactor hipHostRegister test.
2017-05-05 17:29:04 -05: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
Clean up trailing whitespace so as to reduce noise in
#246
.
2017-11-08 00:08:55 +00:00
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
directed tests: Updated to use new hip include path
2016-10-04 22:20:50 +05:30
hipMemcpyDtoD.cpp
Modified tests as per review
2017-11-06 15:13:36 +05:30
hipMemcpyDtoDAsync.cpp
Modified tests as per review
2017-11-06 15:13:36 +05:30
hipMemcpyPeer.cpp
Modified tests as per review
2017-11-06 15:13:36 +05:30
hipMemcpyPeerAsync.cpp
Modified tests as per review
2017-11-06 15:13:36 +05:30
hipMemoryAllocateCoherent.cpp
Add direct test case for threadfence_system workaround
2016-11-11 15:09:43 -06: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
Clean up test to address review feedback.
2017-10-25 16:08:16 -05:00