Since we adjust we adjust the start of the region, amd::BufferRect::end_ is no longer the size, just the offset as to where the region ends.
The actual size of the region is (amd::BufferRect::end_ - amd::BufferRect::start_).
Change-Id: I8425d8bdfb20f485740863813e762e8923d9ee94
[ROCm/clr commit: 4d6e394c73]
Two issues are fixed:
libamdhip64_static.a is not included in package.
cmake generated target files uses installation path of libraries
which are created when the libraries are built and installed.
The CI uses customized installation directory which is not
the package installation directory, thefore the library location
in cmake generated target files differs from the library location
installed from package. This causes rocPRIM build failure since
rocPRIM uses pkg-config which checks library location.
The fix is to fix the library location before adding cmake
generated target files to package.
Change-Id: I4aa2c6138f58df6d4a86301a5c0436edcb19ab70
[ROCm/clr commit: fa66140ee5]
* Disable device side malloc
Currently device side malloc is not working and takes excessive
device memory.
Disable it for now until a working malloc is implemented.
Change-Id: I1ad908c1c53a83752383b4be96688a848642c699
[ROCm/clr commit: d556c3425b]
This is charrypick of 9ead991784
and https://github.com/ROCm-Developer-Tools/HIP/pull/2009
Fix cmake config file
Removed cmake target files under packaging directory.
Merged cmake config .in files for HIP-Clang and HCC as one.
Use cmake generated target files in both install and packaging.
This makes cmake config file consistent for make install and
make package.
Let device side malloc/free return nullptr and trap
Change-Id: I448f3ea2d4934648089bad371debc203f895cba6
[ROCm/clr commit: 4e1d05c4be]
Removed cmake target files under packaging directory.
Merged cmake config .in files for HIP-Clang and HCC as one.
Use cmake generated target files in both install and packaging.
This makes cmake config file consistent for make install and
make package.
Change-Id: Iae1f8ccb5b39c29f54297edf1c5df62eb5a0253d
[ROCm/clr commit: b1ed909f73]
VDI reports the limits in pixels, but user provides the size in bytes.
Make sure both values are in pixels before doing comparisons.
Change-Id: I082c7175c9fa4383e0b0ee38ff8c047c26ff20b4
[ROCm/clr commit: 28da0b89ea]
The following warnings are addressed:
comparison of different enumeration types in switch statement
Change-Id: I6cb3948aeab7287851c57ecc1d4b3a439ab14ec6
[ROCm/clr commit: 524a81fcf5]
Latest llvm already includes the texture/surface rework, but appropriate runtime changes have not been submitted.
Disable all texture related tests until http://gerrit-git.amd.com/c/compute/ec/hip/+/342147 is submitted.
Change-Id: I359c2eac6becdd3ca5110f2140679bd29d8ae54b
[ROCm/clr commit: b291104e7d]
The D3D interop APIs are now declared in the CL headers, so we need to remove our declarations.
The CL headers also automatically include the D3D headers, which need to be included in a specific order (11 -> 10 -> 9), hence why the includes needed to be reshuffled.
Change-Id: I9bd37ceabec82e8bebd1d9c1a5a672ffc95c41d8
[ROCm/clr commit: c4a02ce16f]
- It should be a volatile-qualified member function instead of returning
volatile type.
Change-Id: Id7aaa1953d56151b59e469ef22b9f4280f63bebb
[ROCm/clr commit: 35b001b33a]
This reverts commit 67c6b46cf0.
Reason for revert: German advised againt this change.
Change-Id: Ia1b1b9db60c965b2d9c006bd7d20012a9d7697e1
[ROCm/clr commit: 1b46f2622b]
Support hipLaunchCooperativeKernelMultiDevice()
- Add validation logic for MGPU launches to pass a cuda test
Change-Id: Iccca7fde43493fc3bc6685512d39202271ae3e92
[ROCm/clr commit: 8be723e199]
Support hipLaunchCooperativeKernelMultiDevice()
- Add hipCooperativeLaunchMultiDeviceNoPreSync and
hipCooperativeLaunchMultiDeviceNoPostSync support to pass a cuda test
Change-Id: If518f11ef2636a2235e5df9e77f879d8ced68102
[ROCm/clr commit: 74e98ea447]
These fixes address regressions caused by http://gerrit-git.amd.com/c/compute/ec/hip/+/337601
Currently we're converting a 1D offset into a 3D offset, which doesn't make much sense once you consider the fact that this offset is relative to a different origin than our current 3D offset.
I traced through our blit kernels in VDI - the copy buffer rect path is able to handle immediate offsets in the 3D buffer via the amd::BufferRect::start_ parameter.
Instead of adjusting the offset, simply adjust the start of the region.
Change-Id: Ic8797a2c8ac0ad106f246f61ff06ca1ca03d3058
[ROCm/clr commit: a3613cc6da]
Christophe Paquot
Vlad Sytchenko
Yaxun (Sam) Liu
Evgeny Mankov
Chauncey Hui
kjayapra-amd
Aryan Salmanpour
Payam
Evgeny Shcherbakov
Maneesh Gupta
Aakash Sudhanwa
Sameer Sahasrabuddhe
Saleel Kudchadker
Michael LIAO
Rahul Garg
German Andryeyev