Update manifest to release v5.4.1

Update README.md

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @saadrahim @Rmalavally @amd-aakash @zhang2amd @jlgreathouse

CHANGELOG.md

@@ -0,0 +1,761 @@
+Changelog
+------------------
+# AMD ROCm™ Releases
+
+## AMD  ROCm™ V5.2 Release
+
+AMD ROCm v5.2 is now released. The release documentation is available at https://docs.amd.com.
+
+## AMD  ROCm™ V5.1.3 Release
+
+AMD ROCm v5.1.3 is now released. The release documentation is available at https://docs.amd.com.
+
+## AMD  ROCm™ V5.1.1 Release
+
+AMD ROCm v5.1.1 is now released. The release documentation is available at https://docs.amd.com.
+
+## AMD  ROCm™ V5.1 Release
+
+AMD ROCm v5.1 is now released. The release documentation is available at https://docs.amd.com.
+
+
+## AMD ROCm™ v5.0.2 Release Notes
+
+### Fixed Defects in This Release
+
+The following defects are fixed in the ROCm v5.0.2 release.
+
+#### Issue with hostcall Facility in HIP Runtime
+
+In ROCm v5.0, when using the “assert()” call in a HIP kernel, the compiler may sometimes fail to emit kernel metadata related to the hostcall facility, which results in incomplete initialization of the hostcall facility in the HIP runtime. This can cause the HIP kernel to crash when it attempts to execute the “assert()” call. 
+The root cause was an incorrect check in the compiler to determine whether the hostcall facility is required by the kernel. This is fixed in the ROCm v5.0.2 release. 
+The resolution includes a compiler change, which emits the required metadata by default, unless the compiler can prove that the hostcall facility is not required by the kernel. This ensures that the “assert()” call never fails. 
+
+**Note**: This fix may lead to breakage in some OpenMP offload use cases, which use print inside a target region and result in an abort in device code. The issue will be fixed in a future release. 
+
+#### Compatibility Matrix Updates to ROCm Deep Learning Guide
+
+The compatibility matrix in the AMD Deep Learning Guide is updated for ROCm v5.0.2.
+
+For more information and documentation updates, refer to https://docs.amd.com.
+
+
+
+## AMD ROCm™ v5.0.1 Release Notes
+
+### Deprecations and Warnings
+
+#### Refactor of HIPCC/HIPCONFIG
+
+In prior ROCm releases, by default, the hipcc/hipconfig Perl scripts were used to identify and set target compiler options, target platform, compiler, and runtime appropriately.
+In ROCm v5.0.1, hipcc.bin and hipconfig.bin have been added as the compiled binary implementations of the hipcc and hipconfig. These new binaries are currently a work-in-progress, considered, and marked as experimental. ROCm plans to fully transition to hipcc.bin and hipconfig.bin in the a future ROCm release. The existing hipcc and hipconfig Perl scripts are renamed to hipcc.pl and hipconfig.pl respectively. New top-level hipcc and hipconfig Perl scripts are created, which can switch between the Perl script or the compiled binary based on the environment variable HIPCC_USE_PERL_SCRIPT. 
+In ROCm 5.0.1, by default, this environment variable is set to use hipcc and hipconfig through the Perl scripts.
+Subsequently, Perl scripts will no longer be available in ROCm in a future release.
+
+
+### ROCM DOCUMENTATION UPDATES FOR ROCM 5.0.1
+
+* ROCm Downloads Guide
+
+* ROCm Installation Guide
+
+* ROCm Release Notes
+
+For more information, see https://docs.amd.com.
+
+
+
+## AMD ROCm™ v5.0 Release Notes
+
+
+# ROCm Installation Updates
+
+This document describes the features, fixed issues, and information about downloading and installing the AMD ROCm™ software.
+
+It also covers known issues and deprecations in this release.
+
+## Notice for Open-source and Closed-source ROCm Repositories in Future Releases
+
+To make a distinction between open-source and closed-source components, all ROCm repositories will consist of sub-folders in future releases.
+
+- All open-source components will be placed in the `base-url/<rocm-ver>/main` sub-folder
+- All closed-source components will reside in the `base-url/<rocm-ver>/proprietary`  sub-folder
+
+## List of Supported Operating Systems
+
+The AMD ROCm platform supports the following operating systems:
+
+| **OS-Version (64-bit)** | **Kernel Versions** |
+| --- | --- |
+| CentOS 8.3 | 4.18.0-193.el8 |
+| CentOS 7.9 | 3.10.0-1127 |
+| RHEL 8.5 | 4.18.0-348.7.1.el8\_5.x86\_64 |
+| RHEL 8.4 | 4.18.0-305.el8.x86\_64 |
+| RHEL 7.9 | 3.10.0-1160.6.1.el7 |
+| SLES 15 SP3 | 5.3.18-59.16-default |
+| Ubuntu 20.04.3 | 5.8.0 LTS / 5.11 HWE |
+| Ubuntu 18.04.5 [5.4 HWE kernel] | 5.4.0-71-generic |
+
+### Support for RHEL v8.5
+
+This release extends support for RHEL v8.5.
+
+### Supported GPUs
+
+#### Radeon Pro V620 and W6800 Workstation GPUs
+
+This release extends ROCm support for Radeon Pro V620 and W6800 Workstation GPUs.
+
+- SRIOV virtualization support for Radeon Pro V620
+- KVM Hypervisor (1VF support only) on Ubuntu Host OS with Ubuntu, CentOs, and RHEL Guest
+- Support for ROCm-SMI in an SRIOV environment. For more details, refer to the ROCm SMI API documentation.
+
+**Note:** Radeon Pro v620 is not supported on SLES.
+
+## ROCm Installation Updates for ROCm v5.0
+
+This release has the following ROCm installation enhancements.
+
+### Support for Kernel Mode Driver
+
+In this release, users can install the kernel-mode driver using the Installer method. Some of the ROCm-specific use cases that the installer currently supports are:
+
+- OpenCL (ROCr/KFD based) runtime
+- HIP runtimes
+- ROCm libraries and applications
+- ROCm Compiler and device libraries
+- ROCr runtime and thunk
+- Kernel-mode driver
+
+### Support for Multi-version ROCm Installation and Uninstallation
+
+Users now can install multiple ROCm releases simultaneously on a system using the newly introduced installer script and package manager install mechanism.
+
+Users can also uninstall multi-version ROCm releases using the `amdgpu-uninstall` script and package manager.
+
+### Support for Updating Information on Local Repositories
+
+In this release, the `amdgpu-install` script automates the process of updating local repository information before proceeding to ROCm installation.
+
+### Support for Release Upgrades
+
+Users can now upgrade the existing ROCm installation to specific or latest ROCm releases.
+
+For more details, refer to the AMD ROCm Installation Guide v5.0.
+
+# AMD ROCm V5.0 Documentation Updates
+
+## New AMD ROCm Information Portal – ROCm v4.5 and Above
+
+Beginning ROCm release v5.0, AMD ROCm documentation has a new portal at https://docs.amd.com. This portal consists of ROCm documentation v4.5 and above.
+
+For documentation prior to ROCm v4.5, you may continue to access https://rocmdocs.amd.com.
+
+## Documentation Updates for ROCm 5.0
+
+### Deployment Tools
+
+#### ROCm Data Center Tool Documentation Updates
+
+- ROCm Data Center Tool User Guide
+- ROCm Data Center Tool API Guide
+
+#### ROCm System Management Interface Updates
+
+- System Management Interface Guide
+- System Management Interface API Guide
+
+#### ROCm Command Line Interface Updates
+
+- Command Line Interface Guide
+
+### Machine Learning/AI Documentation Updates
+
+- Deep Learning Guide
+- MIGraphX API Guide
+- MIOpen API Guide
+- MIVisionX API Guide
+
+### ROCm Libraries Documentation Updates
+
+- hipSOLVER User Guide
+- RCCL User Guide
+- rocALUTION User Guide
+- rocBLAS User Guide
+- rocFFT User Guide
+- rocRAND User Guide
+- rocSOLVER User Guide
+- rocSPARSE User Guide
+- rocThrust User Guide
+
+### Compilers and Tools
+
+#### ROCDebugger Documentation Updates
+
+- ROCDebugger User Guide
+- ROCDebugger API Guide
+
+#### ROCTracer
+
+- ROCTracer User Guide
+- ROCTracer API Guide
+
+#### Compilers
+
+- AMD Instinct High Performance Computing and Tuning Guide
+- AMD Compiler Reference Guide
+
+#### HIPify Documentation
+
+- HIPify User Guide
+- HIP Supported CUDA API Reference Guide
+
+#### ROCm Debug Agent
+
+- ROCm Debug Agent Guide
+- System Level Debug Guide
+- ROCm Validation Suite
+
+### Programming Models Documentation
+
+#### HIP Documentation
+
+- HIP Programming Guide
+- HIP API Guide
+- HIP FAQ Guide
+
+#### OpenMP Documentation
+
+- OpenMP Support Guide
+
+### ROCm Glossary
+
+- ROCm Glossary – Terms and Definitions
+
+## AMD ROCm Legacy Documentation Links – ROCm v4.3 and Prior
+
+- For AMD ROCm documentation, see
+
+https://rocmdocs.amd.com/en/latest/
+
+- For installation instructions on supported platforms, see
+
+https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html
+
+- For AMD ROCm binary structure, see
+
+https://rocmdocs.amd.com/en/latest/Installation_Guide/Software-Stack-for-AMD-GPU.html
+
+- For AMD ROCm release history, see
+
+https://rocmdocs.amd.com/en/latest/Current_Release_Notes/ROCm-Version-History.html
+
+# What's New in This Release
+
+## HIP Enhancements
+
+The ROCm v5.0 release consists of the following HIP enhancements.
+
+### HIP Installation Guide Updates
+
+The HIP Installation Guide is updated to include building HIP from source on the NVIDIA platform.
+
+Refer to the HIP Installation Guide v5.0 for more details.
+
+### Managed Memory Allocation
+
+Managed memory, including the `__managed__` keyword, is now supported in the HIP combined host/device compilation. Through unified memory allocation, managed memory allows data to be shared and accessible to both the CPU and GPU using a single pointer. The allocation is managed by the AMD GPU driver using the Linux Heterogeneous Memory Management (HMM) mechanism. The user can call managed memory API hipMallocManaged to allocate a large chunk of HMM memory, execute kernels on a device, and fetch data between the host and device as needed.
+
+**Note:** In a HIP application, it is recommended to do a capability check before calling the managed memory APIs. For example,
+
+```c
+int managed_memory = 0;
+HIPCHECK(hipDeviceGetAttribute(&managed_memory, hipDeviceAttributeManagedMemory, p_gpuDevice));
+
+if (!managed_memory) {
+  printf ("info: managed memory access not supported on the device %d\n Skipped\n", p_gpuDevice);
+} else {
+  HIPCHECK(hipSetDevice(p_gpuDevice));
+  HIPCHECK(hipMallocManaged(&Hmm, N * sizeof(T)));
+  . . .
+}
+```
+
+**Note:** The managed memory capability check may not be necessary; however, if HMM is not supported, managed malloc will fall back to using system memory. Other managed memory API calls will, then, have
+
+Refer to the HIP API documentation for more details on managed memory APIs.
+
+For the application, see [hipMallocManaged.cpp](https://github.com/ROCm-Developer-Tools/HIP/blob/rocm-4.5.x/tests/src/runtimeApi/memory/hipMallocManaged.cpp)
+
+## New Environment Variable
+
+The following new environment variable is added in this release:
+
+| **Environment Variable** | **Value** | **Description** |
+| --- | --- | --- |
+| **HSA\_COOP\_CU\_COUNT** | 0 or 1 (default is 0) | Some processors support more compute units than can reliably be used in a cooperative dispatch. Setting the environment variable HSA\_COOP\_CU\_COUNT to 1 will cause ROCr to return the correct CU count for cooperative groups through the HSA\_AMD\_AGENT\_INFO\_COOPERATIVE\_COMPUTE\_UNIT\_COUNT attribute of hsa\_agent\_get\_info(). Setting HSA\_COOP\_CU\_COUNT to other values, or leaving it unset, will cause ROCr to return the same CU count for the attributes HSA\_AMD\_AGENT\_INFO\_COOPERATIVE\_COMPUTE\_UNIT\_COUNT and HSA\_AMD\_AGENT\_INFO\_COMPUTE\_UNIT\_COUNT. Future ROCm releases will make HSA\_COOP\_CU\_COUNT=1 the default.
+ |
+
+## ROCm Math and Communication Libraries
+
+| **Library** | **Changes** |
+| --- | --- |
+| **rocBLAS** | **Added** <ul><li>Added rocblas\_get\_version\_string\_size convenience function</li><li>Added rocblas\_xtrmm\_outofplace, an out-of-place version of rocblas\_xtrmm</li><li>Added hpl and trig initialization for gemm\_ex to rocblas-bench</li><li>Added source code gemm. It can be used as an alternative to Tensile for debugging and development</li><li>Added option `ROCM_MATHLIBS_API_USE_HIP_COMPLEX` to opt-in to use hipFloatComplex and hipDoubleComplex</li></ul> **Optimizations** <ul><li>Improved performance of non-batched and batched single-precision GER for size m > 1024. Performance enhanced by 5-10% measured on a MI100 (gfx908) GPU.</li><li>Improved performance of non-batched and batched HER for all sizes and data types. Performance enhanced by 2-17% measured on a MI100 (gfx908) GPU.</li></ul> **Changed** <ul><li>Instantiate templated rocBLAS functions to reduce size of librocblas.so</li><li>Removed static library dependency on msgpack</li><li>Removed boost dependencies for clients</li></ul> **Fixed** <ul><li>Option to install script to build only rocBLAS clients with a pre-built rocBLAS library</li><li>Correctly set output of nrm2\_batched\_ex and nrm2\_strided\_batched\_ex when given bad input</li><li>Fix for dgmm with side == rocblas\_side\_left and a negative incx</li><li>Fixed out-of-bounds read for small trsm</li><li>Fixed numerical checking for tbmv\_strided\_batched</li></ul> |
+| | |
+| **hipBLAS** | **Added** <ul><li>Added rocSOLVER functions to hipblas-bench</li><li>Added option `ROCM_MATHLIBS_API_USE_HIP_COMPLEX` to opt-in to use hipFloatComplex and hipDoubleComplex</li><li>Added compilation warning for future trmm changes</li><li>Added documentation to hipblas.h</li><li>Added option to forgo pivoting for getrf and getri when ipiv is nullptr</li><li>Added code coverage option</li></ul> **Fixed** <ul><li>Fixed use of incorrect `HIP_PATH` when building from source.</li><li>Fixed windows packaging</li><li>Allowing negative increments in hipblas-bench</li><li>Removed boost dependency</li></ul> |
+| | |
+| **rocFFT** | **Changed** <ul><li>Enabled runtime compilation of single FFT kernels > length 1024.</li><li>Re-aligned split device library into 4 roughly equal libraries.</li><li>Implemented the FuseShim framework to replace the original OptimizePlan</li><li>Implemented the generic buffer-assignment framework. The buffer assignment is no longer performed by each node. A generic algorithm is designed to test and pick the best assignment path. With the help of FuseShim, more kernel-fusions are achieved.</li><li>Do not read the imaginary part of the DC and Nyquist modes for even-length complex-to-real transforms.</li></ul> **Optimizations** <ul><li>Optimized twiddle-conjugation; complex-to-complex inverse transforms have similar performance to foward transforms now.</li><li>Improved performance of single-kernel small 2D transforms.</li></ul> |
+| | |
+| **hipFFT** | **Fixed** <ul><li>Fixed incorrect reporting of rocFFT version.</li></ul> **Changed** <ul><li>Unconditionally enabled callback functionality. On the CUDA backend, callbacks only run correctly when hipFFT is built as a static library, and is linked against the static cuFFT library.</li></ul> |
+| | |
+| **rocSPARSE** | **Added** <ul><li>csrmv, coomv, ellmv, hybmv for (conjugate) transposed matricescsrmv for symmetric matrices</li></ul> **Changed** <ul><li>spmm\_ex is now deprecated and will be removed in the next major release</li></ul> **Improved** <ul><li>Optimization for gtsv</li></ul> |
+| | |
+| **hipSPARSE** | **Added** <ul><li>Added (conjugate) transpose support for csrmv, hybmv and spmv routines</li></ul> |
+| | |
+| **rocALUTION** | **Changed** <ul><li>Removed deprecated GlobalPairwiseAMG class, please use PairwiseAMG instead.</li></ul> **Improved** <ul><li>Improved documentation</li></ul> |
+| | |
+| **rocTHRUST** | **Updates** <ul><li>Updated to match upstream Thrust 1.13.0</li><li>Updated to match upstream Thrust 1.14.0</li><li>Added async scan</li></ul> **Changed** <ul><li>Scan algorithms: inclusive\_scan now uses the input-type as accumulator-type, exclusive\_scan uses initial-value-type. This particularly changes behaviour of small-size input types with large-size output types (e.g. short input, int output). And low-res input with high-res output (e.g. float input, double output)</li></ul> |
+| | |
+| **rocSOLVER** | **Added** <ul><li>Symmetric matrix factorizations: <ul><li>LASYF</li><li>SYTF2, SYTRF (with batched and strided\_batched versions)</li></ul><li>Added rocsolver\_get\_version\_string\_size to help with version string queries</li><li>Added rocblas\_layer\_mode\_ex and the ability to print kernel calls in the trace and profile logs</li><li>Expanded batched and strided\_batched sample programs.</li></ul> **Optimizations** <ul><li>Improved general performance of LU factorization</li><li>Increased parallelism of specialized kernels when compiling from source, reducing build times on multi-core systems.</li></ul> **Changed** <ul><li>The rocsolver-test client now prints the rocSOLVER version used to run the tests, rather than the version used to build them</li><li>The rocsolver-bench client now prints the rocSOLVER version used in the benchmark</li></ul> **Fixed** <ul><li>Added missing stdint.h include to rocsolver.h</li></ul> |
+| | |
+| **hipSOLVER** | **Added** <ul><li>Added SYTRF functions: hipsolverSsytrf\_bufferSize, hipsolverDsytrf\_bufferSize, hipsolverCsytrf\_bufferSize, hipsolverZsytrf\_bufferSize, hipsolverSsytrf, hipsolverDsytrf, hipsolverCsytrf, hipsolverZsytrf</li></ul> **Fixed** <ul><li>Fixed use of incorrect `HIP_PATH` when building from source</li></ul> |
+| | |
+| **RCCL** | **Added** <ul><li>Compatibility with NCCL 2.10.3</li></ul> **Known issues** <ul><li>Managed memory is not currently supported for clique-based kernels</li></ul> |
+| | |
+| **hipCUB** | **Fixed** <ul><li>Added missing includes to hipcub.hpp</li></ul> **Added** <ul><li>Bfloat16 support to test cases (device\_reduce & device\_radix\_sort)</li><li>Device merge sort</li><li>Block merge sort</li><li>API update to CUB 1.14.0</li></ul> **Changed** <ul><li>The SetupNVCC.cmake automatic target selector select all of the capabalities of all available card for NVIDIA backend.</li></ul> |
+| | |
+| **rocPRIM** | **Fixed** <ul><li>Enable bfloat16 tests and reduce threshold for bfloat16</li><li>Fix device scan limit\_size feature</li><li>Non-optimized builds no longer trigger local memory limit errors</li></ul> **Added** <ul><li>Scan size limit feature</li><li>Reduce size limit feature</li><li>Transform size limit feature</li><li>Add block\_load\_striped and block\_store\_striped</li><li>Add gather\_to\_blocked to gather values from other threads into a blocked arrangement</li><li>The block sizes for device merge sorts initial block sort and its merge steps are now separate in its kernel config (the block sort step supports multiple items per thread)</li></ul> **Changed** <ul><li>size\_limit for scan, reduce and transform can now be set in the config struct instead of a parameter</li><li>device\_scan and device\_segmented\_scan: inclusive\_scan now uses the input-type as accumulator-type, exclusive\_scan uses initial-value-type. This particularly changes behaviour of small-size input types with large-size output types (e.g. short input, int output) and low-res input with high-res output (e.g. float input, double output)</li><li>Revert old Fiji workaround, because the issue was solved at compiler side</li><li>Update README cmake minimum version number</li><li>Block sort support multiple items per thread. Currently only powers of two block sizes, and items per threads are supported and only for full blocks</li><li>Bumped the minimum required version of CMake to 3.16</li></ul> **Known issues** <ul><li>Unit tests may soft hang on MI200 when running in hipMallocManaged mode.</li><li>device\_segmented\_radix\_sort, device\_scan unit tests failing for HIP on WindowsReduceEmptyInput cause random failure with bfloat16</li><li>Managed memory is not currently supported for clique-based kernels</li></ul> |
+
+## System Management Interface
+
+### Clock Throttling for GPU Events
+
+This feature lists GPU events as they occur in real-time and can be used with _kfdtest_ to produce _vm\_fault_ events for testing.
+
+The command can be called with either &quot; `-e` or `--showevents` like this:
+
+    -e [EVENT [EVENT ...]], --showevents [EVENT [EVENT ...]]  Show event list
+
+Where `EVENT` is any list combination of `VM_FAULT`, `THERMAL_THROTTLE`, or `GPU_RESET` and is NOT case sensitive.
+
+**Note:** If no event arguments are passed, all events will be watched by default.
+
+#### CLI Commands
+
+```
+$ rocm-smi --showevents vm_fault thermal_throttle gpu_reset
+
+======================= ROCm System Management Interface =======================
+================================= Show Events ==================================
+press 'q' or 'ctrl + c' to quit
+DEVICE		TIME		TYPE		DESCRIPTION
+
+============================= End of ROCm SMI Log ==============================
+```
+
+(Run kfdtest in another window to test for vm\_fault events.)
+
+**Note:** Unlike other rocm-smi CLI commands, this command does not quit unless specified by the user. Users may press either `q` or `ctrl + c` to quit.
+
+### Display XGMI Bandwidth Between Nodes
+
+The _rsmi\_minmax\_bandwidth\_get_ API reads the HW Topology file and displays bandwidth (min-max) between any two NUMA nodes in a matrix format.
+
+The Command Line Interface (CLI) command can be called as follows:
+
+```
+$ rocm-smi --shownodesbw
+
+======================= ROCm System Management Interface =======================
+================================== Bandwidth ===================================
+GPU0 GPU1 GPU2 GPU3 GPU4 GPU5 GPU6 GPU7
+GPU0 N/A 50000-200000 50000-50000 0-0 0-0 0-0 50000-100000 0-0
+GPU1 50000-200000 N/A 0-0 50000-50000 0-0 50000-50000 0-0 0-0
+GPU2 50000-50000 0-0 N/A 50000-200000 50000-100000 0-0 0-0 0-0
+GPU3 0-0 50000-50000 50000-200000 N/A 0-0 0-0 0-0 50000-50000
+GPU4 0-0 0-0 50000-100000 0-0 N/A 50000-200000 50000-50000 0-0
+GPU5 0-0 50000-50000 0-0 0-0 50000-200000 N/A 0-0 50000-50000
+GPU6 50000-100000 0-0 0-0 0-0 50000-50000 0-0 N/A 50000-200000
+GPU7 0-0 0-0 0-0 50000-50000 0-0 50000-50000 50000-200000 N/A
+Format: min-max; Units: mps
+============================= End of ROCm SMI Log ==============================
+```
+
+The sample output above shows the maximum theoretical xgmi bandwidth between 2 numa nodes,
+
+**Note:** "0-0" min-max bandwidth indicates devices are not connected directly.
+
+### P2P Connection Status
+
+The _rsmi\_is\_p2p\_accessible_ API returns "True" if P2P can be implemented between two nodes, and returns "False" if P2P cannot be implemented between the two nodes.
+
+The Command Line Interface command can be called as follows:
+
+    rocm-smi --showtopoaccess
+
+Sample Output:
+
+```
+$ rocm-smi --showtopoaccess
+======================= ROCm System Management Interface =======================
+===================== Link accessibility between two GPUs ======================
+GPU0 GPU1
+GPU0 True True
+GPU1 True True
+============================= End of ROCm SMI Log ==============================
+```
+
+# Breaking Changes
+
+## Runtime Breaking Change
+
+Re-ordering of the enumerated type in hip\_runtime\_api.h to better match NV.  See below for the difference in enumerated types.
+
+ROCm software will be affected if any of the defined enums listed below are used in the code.  Applications built with ROCm v5.0 enumerated types will work with a ROCm 4.5.2 driver. However, an undefined behavior error will occur with a ROCm v4.5.2 application that uses these enumerated types with a ROCm 5.0 runtime.
+
+```c
+typedef enum hipDeviceAttribute_t {
+  hipDeviceAttributeMaxThreadsPerBlock, // Maximum number of threads per block.
+  hipDeviceAttributeMaxBlockDimX, // Maximum x-dimension of a block.
+  hipDeviceAttributeMaxBlockDimY, // Maximum y-dimension of a block.
+  hipDeviceAttributeMaxBlockDimZ, // Maximum z-dimension of a block.
+  hipDeviceAttributeMaxGridDimX, // Maximum x-dimension of a grid.
+  hipDeviceAttributeMaxGridDimY, // Maximum y-dimension of a grid.
+  hipDeviceAttributeMaxGridDimZ, // Maximum z-dimension of a grid.
+  hipDeviceAttributeMaxSharedMemoryPerBlock, // Maximum shared memory available per block in bytes.
+  hipDeviceAttributeTotalConstantMemory, // Constant memory size in bytes.
+  hipDeviceAttributeWarpSize, // Warp size in threads.
+  hipDeviceAttributeMaxRegistersPerBlock, // Maximum number of 32-bit registers available to a
+                                          // thread block. This number is shared by all thread
+                                          // blocks simultaneously resident on a
+                                          // multiprocessor.
+  hipDeviceAttributeClockRate, // Peak clock frequency in kilohertz.
+  hipDeviceAttributeMemoryClockRate, // Peak memory clock frequency in kilohertz.
+  hipDeviceAttributeMemoryBusWidth, // Global memory bus width in bits.
+  hipDeviceAttributeMultiprocessorCount, // Number of multiprocessors on the device.
+  hipDeviceAttributeComputeMode, // Compute mode that device is currently in.
+  hipDeviceAttributeL2CacheSize, // Size of L2 cache in bytes. 0 if the device doesn't have L2
+                                 // cache.
+  hipDeviceAttributeMaxThreadsPerMultiProcessor, // Maximum resident threads per
+                                                 // multiprocessor.
+  hipDeviceAttributeComputeCapabilityMajor, // Major compute capability version number.
+  hipDeviceAttributeComputeCapabilityMinor, // Minor compute capability version number.
+  hipDeviceAttributeConcurrentKernels, // Device can possibly execute multiple kernels
+                                       // concurrently.
+  hipDeviceAttributePciBusId, // PCI Bus ID.
+  hipDeviceAttributePciDeviceId, // PCI Device ID.
+  hipDeviceAttributeMaxSharedMemoryPerMultiprocessor, // Maximum Shared Memory Per
+                                                      // Multiprocessor.
+  hipDeviceAttributeIsMultiGpuBoard, // Multiple GPU devices.
+  hipDeviceAttributeIntegrated, // iGPU
+  hipDeviceAttributeCooperativeLaunch, // Support cooperative launch
+  hipDeviceAttributeCooperativeMultiDeviceLaunch, // Support cooperative launch on multiple devices
+  hipDeviceAttributeMaxTexture1DWidth, // Maximum number of elements in 1D images
+  hipDeviceAttributeMaxTexture2DWidth, // Maximum dimension width of 2D images in image elements
+  hipDeviceAttributeMaxTexture2DHeight, // Maximum dimension height of 2D images in image elements
+  hipDeviceAttributeMaxTexture3DWidth, // Maximum dimension width of 3D images in image elements
+  hipDeviceAttributeMaxTexture3DHeight, // Maximum dimensions height of 3D images in image elements
+  hipDeviceAttributeMaxTexture3DDepth, // Maximum dimensions depth of 3D images in image elements
+  hipDeviceAttributeCudaCompatibleBegin = 0,
+  hipDeviceAttributeHdpMemFlushCntl, // Address of the HDP\_MEM\_COHERENCY\_FLUSH\_CNTL register
+  hipDeviceAttributeHdpRegFlushCntl, // Address of the HDP\_REG\_COHERENCY\_FLUSH\_CNTL register
+  hipDeviceAttributeEccEnabled = hipDeviceAttributeCudaCompatibleBegin, // Whether ECC support is enabled.
+  hipDeviceAttributeAccessPolicyMaxWindowSize, // Cuda only. The maximum size of the window policy in bytes.
+  hipDeviceAttributeAsyncEngineCount, // Cuda only. Asynchronous engines number.
+  hipDeviceAttributeCanMapHostMemory, // Whether host memory can be mapped into device address space
+  hipDeviceAttributeCanUseHostPointerForRegisteredMem, // Cuda only. Device can access host registered memory
+  // at the same virtual address as the CPU
+  hipDeviceAttributeClockRate, // Peak clock frequency in kilohertz.
+  hipDeviceAttributeComputeMode, // Compute mode that device is currently in.
+  hipDeviceAttributeComputePreemptionSupported, // Cuda only. Device supports Compute Preemption.
+  hipDeviceAttributeConcurrentKernels, // Device can possibly execute multiple kernels concurrently.
+  hipDeviceAttributeConcurrentManagedAccess, // Device can coherently access managed memory concurrently with the CPU
+  hipDeviceAttributeCooperativeLaunch, // Support cooperative launch
+  hipDeviceAttributeCooperativeMultiDeviceLaunch, // Support cooperative launch on multiple devices
+  hipDeviceAttributeDeviceOverlap, // Cuda only. Device can concurrently copy memory and execute a kernel.
+                                   // Deprecated. Use instead asyncEngineCount.
+  hipDeviceAttributeDirectManagedMemAccessFromHost, // Host can directly access managed memory on
+                                                    // the device without migration
+  hipDeviceAttributeGlobalL1CacheSupported, // Cuda only. Device supports caching globals in L1
+  hipDeviceAttributeHostNativeAtomicSupported, // Cuda only. Link between the device and the host supports native atomic operations
+  hipDeviceAttributeIntegrated, // Device is integrated GPU
+  hipDeviceAttributeIsMultiGpuBoard, // Multiple GPU devices.
+  hipDeviceAttributeKernelExecTimeout, // Run time limit for kernels executed on the device
+  hipDeviceAttributeL2CacheSize, // Size of L2 cache in bytes. 0 if the device doesn&#39;t have L2 cache.
+  hipDeviceAttributeLocalL1CacheSupported, // caching locals in L1 is supported
+  hipDeviceAttributeLuid, // Cuda only. 8-byte locally unique identifier in 8 bytes. Undefined on TCC and non-Windows platforms
+  hipDeviceAttributeLuidDeviceNodeMask, // Cuda only. Luid device node mask. Undefined on TCC and non-Windows platforms
+  hipDeviceAttributeComputeCapabilityMajor, // Major compute capability version number.
+  hipDeviceAttributeManagedMemory, // Device supports allocating managed memory on this system
+  hipDeviceAttributeMaxBlocksPerMultiProcessor, // Cuda only. Max block size per multiprocessor
+  hipDeviceAttributeMaxBlockDimX, // Max block size in width.
+  hipDeviceAttributeMaxBlockDimY, // Max block size in height.
+  hipDeviceAttributeMaxBlockDimZ, // Max block size in depth.
+  hipDeviceAttributeMaxGridDimX, // Max grid size in width.
+  hipDeviceAttributeMaxGridDimY, // Max grid size in height.
+  hipDeviceAttributeMaxGridDimZ, // Max grid size in depth.
+  hipDeviceAttributeMaxSurface1D, // Maximum size of 1D surface.
+  hipDeviceAttributeMaxSurface1DLayered, // Cuda only. Maximum dimensions of 1D layered surface.
+  hipDeviceAttributeMaxSurface2D, // Maximum dimension (width, height) of 2D surface.
+  hipDeviceAttributeMaxSurface2DLayered, // Cuda only. Maximum dimensions of 2D layered surface.
+  hipDeviceAttributeMaxSurface3D, // Maximum dimension (width, height, depth) of 3D surface.
+  hipDeviceAttributeMaxSurfaceCubemap, // Cuda only. Maximum dimensions of Cubemap surface.
+  hipDeviceAttributeMaxSurfaceCubemapLayered, // Cuda only. Maximum dimension of Cubemap layered surface.
+  hipDeviceAttributeMaxTexture1DWidth, // Maximum size of 1D texture.
+  hipDeviceAttributeMaxTexture1DLayered, // Cuda only. Maximum dimensions of 1D layered texture.
+  hipDeviceAttributeMaxTexture1DLinear, // Maximum number of elements allocatable in a 1D linear texture.
+                                        // Use cudaDeviceGetTexture1DLinearMaxWidth() instead on Cuda.
+  hipDeviceAttributeMaxTexture1DMipmap, // Cuda only. Maximum size of 1D mipmapped texture.
+  hipDeviceAttributeMaxTexture2DWidth, // Maximum dimension width of 2D texture.
+  hipDeviceAttributeMaxTexture2DHeight, // Maximum dimension hight of 2D texture.
+  hipDeviceAttributeMaxTexture2DGather, // Cuda only. Maximum dimensions of 2D texture if gather operations performed.
+  hipDeviceAttributeMaxTexture2DLayered, // Cuda only. Maximum dimensions of 2D layered texture.
+  hipDeviceAttributeMaxTexture2DLinear, // Cuda only. Maximum dimensions (width, height, pitch) of 2D textures bound to pitched memory.
+  hipDeviceAttributeMaxTexture2DMipmap, // Cuda only. Maximum dimensions of 2D mipmapped texture.
+  hipDeviceAttributeMaxTexture3DWidth, // Maximum dimension width of 3D texture.
+  hipDeviceAttributeMaxTexture3DHeight, // Maximum dimension height of 3D texture.
+  hipDeviceAttributeMaxTexture3DDepth, // Maximum dimension depth of 3D texture.
+  hipDeviceAttributeMaxTexture3DAlt, // Cuda only. Maximum dimensions of alternate 3D texture.
+  hipDeviceAttributeMaxTextureCubemap, // Cuda only. Maximum dimensions of Cubemap texture
+  hipDeviceAttributeMaxTextureCubemapLayered, // Cuda only. Maximum dimensions of Cubemap layered texture.
+  hipDeviceAttributeMaxThreadsDim, // Maximum dimension of a block
+  hipDeviceAttributeMaxThreadsPerBlock, // Maximum number of threads per block.
+  hipDeviceAttributeMaxThreadsPerMultiProcessor, // Maximum resident threads per multiprocessor.
+  hipDeviceAttributeMaxPitch, // Maximum pitch in bytes allowed by memory copies
+  hipDeviceAttributeMemoryBusWidth, // Global memory bus width in bits.
+  hipDeviceAttributeMemoryClockRate, // Peak memory clock frequency in kilohertz.
+  hipDeviceAttributeComputeCapabilityMinor, // Minor compute capability version number.
+  hipDeviceAttributeMultiGpuBoardGroupID, // Cuda only. Unique ID of device group on the same multi-GPU board
+  hipDeviceAttributeMultiprocessorCount, // Number of multiprocessors on the device.
+  hipDeviceAttributeName, // Device name.
+  hipDeviceAttributePageableMemoryAccess, // Device supports coherently accessing pageable memory
+                                          // without calling hipHostRegister on it
+  hipDeviceAttributePageableMemoryAccessUsesHostPageTables, // Device accesses pageable memory via the host&#39;s page tables
+  hipDeviceAttributePciBusId, // PCI Bus ID.
+  hipDeviceAttributePciDeviceId, // PCI Device ID.
+  hipDeviceAttributePciDomainID, // PCI Domain ID.
+  hipDeviceAttributePersistingL2CacheMaxSize, // Cuda11 only. Maximum l2 persisting lines capacity in bytes
+  hipDeviceAttributeMaxRegistersPerBlock, // 32-bit registers available to a thread block. This number is shared
+                                          // by all thread blocks simultaneously resident on a multiprocessor.
+  hipDeviceAttributeMaxRegistersPerMultiprocessor, // 32-bit registers available per block.
+  hipDeviceAttributeReservedSharedMemPerBlock, // Cuda11 only. Shared memory reserved by CUDA driver per block.
+  hipDeviceAttributeMaxSharedMemoryPerBlock, // Maximum shared memory available per block in bytes.
+  hipDeviceAttributeSharedMemPerBlockOptin, // Cuda only. Maximum shared memory per block usable by special opt in.
+  hipDeviceAttributeSharedMemPerMultiprocessor, // Cuda only. Shared memory available per multiprocessor.
+  hipDeviceAttributeSingleToDoublePrecisionPerfRatio, // Cuda only. Performance ratio of single precision to double precision.
+  hipDeviceAttributeStreamPrioritiesSupported, // Cuda only. Whether to support stream priorities.
+  hipDeviceAttributeSurfaceAlignment, // Cuda only. Alignment requirement for surfaces
+  hipDeviceAttributeTccDriver, // Cuda only. Whether device is a Tesla device using TCC driver
+  hipDeviceAttributeTextureAlignment, // Alignment requirement for textures
+  hipDeviceAttributeTexturePitchAlignment, // Pitch alignment requirement for 2D texture references bound to pitched memory;
+  hipDeviceAttributeTotalConstantMemory, // Constant memory size in bytes.
+  hipDeviceAttributeTotalGlobalMem, // Global memory available on devicice.
+  hipDeviceAttributeUnifiedAddressing, // Cuda only. An unified address space shared with the host.
+  hipDeviceAttributeUuid, // Cuda only. Unique ID in 16 byte.
+  hipDeviceAttributeWarpSize, // Warp size in threads.
+  hipDeviceAttributeMaxPitch, // Maximum pitch in bytes allowed by memory copies
+  hipDeviceAttributeTextureAlignment, //Alignment requirement for textures
+  hipDeviceAttributeTexturePitchAlignment, //Pitch alignment requirement for 2D texture references bound to pitched memory;
+  hipDeviceAttributeKernelExecTimeout, //Run time limit for kernels executed on the device
+  hipDeviceAttributeCanMapHostMemory, //Device can map host memory into device address space
+  hipDeviceAttributeEccEnabled, //Device has ECC support enabled
+  hipDeviceAttributeCudaCompatibleEnd = 9999,
+  hipDeviceAttributeAmdSpecificBegin = 10000,
+  hipDeviceAttributeCooperativeMultiDeviceUnmatchedFunc, // Supports cooperative launch on multiple
+                                                         // devices with unmatched functions
+  hipDeviceAttributeCooperativeMultiDeviceUnmatchedGridDim, // Supports cooperative launch on multiple
+                                                            // devices with unmatched grid dimensions
+  hipDeviceAttributeCooperativeMultiDeviceUnmatchedBlockDim, // Supports cooperative launch on multiple
+                                                             // devices with unmatched block dimensions
+  hipDeviceAttributeCooperativeMultiDeviceUnmatchedSharedMem, // Supports cooperative launch on multiple
+                                                              // devices with unmatched shared memories
+  hipDeviceAttributeAsicRevision, // Revision of the GPU in this device
+  hipDeviceAttributeManagedMemory, // Device supports allocating managed memory on this system
+  hipDeviceAttributeDirectManagedMemAccessFromHost, // Host can directly access managed memory on
+                                                    //  the device without migration
+  hipDeviceAttributeConcurrentManagedAccess, // Device can coherently access managed memory
+                                             // concurrently with the CPU
+  hipDeviceAttributePageableMemoryAccess, // Device supports coherently accessing pageable memory
+                                          // without calling hipHostRegister on it
+  hipDeviceAttributePageableMemoryAccessUsesHostPageTables, // Device accesses pageable memory via
+                                                            // the host's page tables
+  hipDeviceAttributeCanUseStreamWaitValue // '1' if Device supports hipStreamWaitValue32() and
+                                          // hipStreamWaitValue64(), '0' otherwise.
+  hipDeviceAttributeClockInstructionRate = hipDeviceAttributeAmdSpecificBegin, // Frequency in khz of the timer used by the device-side "clock"
+  hipDeviceAttributeArch, // Device architecture
+  hipDeviceAttributeMaxSharedMemoryPerMultiprocessor, // Maximum Shared Memory PerMultiprocessor.
+  hipDeviceAttributeGcnArch, // Device gcn architecture
+  hipDeviceAttributeGcnArchName, // Device gcnArch name in 256 bytes
+  hipDeviceAttributeHdpMemFlushCntl, // Address of the HDP_MEM_COHERENCY_FLUSH_CNTL register
+  hipDeviceAttributeHdpRegFlushCntl, // Address of the HDP_REG_COHERENCY_FLUSH_CNTL register
+  hipDeviceAttributeCooperativeMultiDeviceUnmatchedFunc, // Supports cooperative launch on multiple
+                                                         // devices with unmatched functions
+  hipDeviceAttributeCooperativeMultiDeviceUnmatchedGridDim, // Supports cooperative launch on multiple
+                                                            // devices with unmatched grid dimensions
+  hipDeviceAttributeCooperativeMultiDeviceUnmatchedBlockDim, // Supports cooperative launch on multiple
+                                                             // devices with unmatched block dimensions
+  hipDeviceAttributeCooperativeMultiDeviceUnmatchedSharedMem, // Supports cooperative launch on multiple
+                                                              // devices with unmatched shared memories
+  hipDeviceAttributeIsLargeBar, // Whether it is LargeBar
+  hipDeviceAttributeAsicRevision, // Revision of the GPU in this device
+  hipDeviceAttributeCanUseStreamWaitValue, // '1' if Device supports hipStreamWaitValue32() and
+                                           // hipStreamWaitValue64() , '0' otherwise.
+  hipDeviceAttributeAmdSpecificEnd = 19999,
+  hipDeviceAttributeVendorSpecificBegin = 20000,   // Extended attributes for vendors
+} hipDeviceAttribute_t;
+```
+
+# Known Issues in This Release
+
+## Incorrect dGPU Behavior When Using AMDVBFlash Tool
+
+The AMDVBFlash tool, used for flashing the VBIOS image to dGPU, does not communicate with the ROM Controller specifically when the driver is present. This is because the driver, as part of its runtime power management feature, puts the dGPU to a sleep state.
+
+As a workaround, users can run `amdgpu.runpm=0`, which temporarily disables the runtime power management feature from the driver and dynamically changes some power control-related sysfs files.
+
+## Issue with START Timestamp in ROCProfiler
+
+Users may encounter an issue with the enabled timestamp functionality for monitoring one or multiple counters. ROCProfiler outputs the following four timestamps for each kernel:
+
+- Dispatch
+- Start
+- End
+- Complete
+
+**Issue**
+
+This defect is related to the Start timestamp functionality, which incorrectly shows an earlier time than the Dispatch timestamp.
+
+To reproduce the issue,
+
+1. Enable timing using the `--timestamp on` flag.
+2. Use the `-i` option with the input filename that contains the name of the counter(s) to monitor.
+3. Run the program.
+4. Check the output result file.
+
+**Current behavior**
+
+BeginNS is lower than DispatchNS, which is incorrect.
+
+**Expected behavior**
+
+The correct order is:
+
+_Dispatch < Start < End < Complete_
+
+Users cannot use ROCProfiler to measure the time spent on each kernel because of the incorrect timestamp with counter collection enabled.
+
+**Recommended Workaround**
+
+Users are recommended to collect kernel execution timestamps without monitoring counters, as follows:
+
+1. Enable timing using the `--timestamp on` flag, and run the application.
+2. Rerun the application using the `-i` option with the input filename that contains the name of the counter(s) to monitor, and save this to a different output file using the `-o` flag.
+3. Check the output result file from step 1.
+4. The order of timestamps correctly displays as:
+
+_DispathNS < BeginNS < EndNS < CompleteNS_
+
+1. Users can find the values of the collected counters in the output file generated in step 2.
+
+## Radeon Pro V620 and W6800 Workstation GPUs
+
+### No Support for SMI and ROCDebugger on SRIOV
+
+System Management Interface (SMI) and ROCDebugger are not supported in the SRIOV environment on any GPU. For more information, refer to the Systems Management Interface documentation.
+
+# Deprecations and Warnings in This Release
+
+## ROCm Libraries Changes – Deprecations and Deprecation Removal
+
+- The hipfft.h header is now provided only by the hipfft package.  Up to ROCm 5.0, users would get hipfft.h in the rocfft package too.
+- The GlobalPairwiseAMG class is now entirely removed, users should use the PairwiseAMG class instead.
+- The rocsparse\_spmm signature in 5.0 was changed to match that of rocsparse\_spmm\_ex.  In 5.0, rocsparse\_spmm\_ex is still present, but deprecated.  Signature diff for rocsparse\_spmm
+
+### _rocsparse\_spmm_ in 5.0
+
+```c
+rocsparse_status rocsparse_spmm(rocsparse_handle            handle,
+                                rocsparse_operation         trans_A,
+                                rocsparse_operation         trans_B,
+                                const void*                 alpha,
+                                const rocsparse_spmat_descr mat_A,
+                                const rocsparse_dnmat_descr mat_B,
+                                const void*                 beta,
+                                const rocsparse_dnmat_descr mat_C,
+                                rocsparse_datatype          compute_type,
+                                rocsparse_spmm_alg          alg,
+                                rocsparse_spmm_stage        stage,
+                                size_t*                     buffer_size,
+                                void*                       temp_buffer);
+```
+
+### _rocsparse\_spmm_ in 4.0
+
+```c
+rocsparse_status rocsparse_spmm(rocsparse_handle            handle,
+                                rocsparse_operation         trans_A,
+                                rocsparse_operation         trans_B,
+                                const void*                 alpha,
+                                const rocsparse_spmat_descr mat_A,
+                                const rocsparse_dnmat_descr mat_B,
+                                const void*                 beta,
+                                const rocsparse_dnmat_descr mat_C,
+                                rocsparse_datatype          compute_type,
+                                rocsparse_spmm_alg          alg,
+                                size_t*                     buffer_size,
+                                void*                       temp_buffer);
+```
+
+## HIP API Deprecations and Warnings
+
+### Warning - Arithmetic Operators of HIP Complex and Vector Types
+
+In this release, arithmetic operators of HIP complex and vector types are deprecated.
+
+- As alternatives to arithmetic operators of HIP complex types, users can use arithmetic operators of std::complex types.
+- As alternatives to arithmetic operators of HIP vector types, users can use the operators of the native clang vector type associated with the data member of HIP vector types.
+
+During the deprecation, two macros `__HIP_ENABLE_COMPLEX_OPERATORS` and `__HIP_ENABLE_VECTOR_OPERATORS` are provided to allow users to conditionally enable arithmetic operators of HIP complex or vector types.
+
+Note, the two macros are mutually exclusive and, by default, set to off.
+
+The arithmetic operators of HIP complex and vector types will be removed in a future release.
+
+Refer to the HIP API Guide for more information.
+
+### Refactor of HIPCC/HIPCONFIG
+
+In prior ROCm releases, by default, the hipcc/hipconfig Perl scripts were used to identify and set target compiler options, target platform, compiler, and runtime appropriately.
+
+In ROCm v5.0, hipcc.bin and hipconfig.bin have been added as the compiled binary implementations of the hipcc and hipconfig. These new binaries are currently a work-in-progress, considered, and marked as experimental. ROCm plans to fully transition to hipcc.bin and hipconfig.bin in the a future ROCm release. The existing hipcc and hipconfig Perl scripts are renamed to hipcc.pl and hipconfig.pl respectively. New top-level hipcc and hipconfig Perl scripts are created, which can switch between the Perl script or the compiled binary based on the environment variable `HIPCC_USE_PERL_SCRIPT`.
+
+In ROCm 5.0, by default, this environment variable is set to use hipcc and hipconfig through the Perl scripts.
+
+Subsequently, Perl scripts will no longer be available in ROCm in a future release.
+
+## Warning - Compiler-Generated Code Object Version 4 Deprecation
+
+Support for loading compiler-generated code object version 4 will be deprecated in a future release with no release announcement and replaced with code object 5 as the default version.
+
+The current default is code object version 4.
+
+## Warning - MIOpenTensile Deprecation
+
+MIOpenTensile will be deprecated in a future release.
+
+
+
+
+
+Archived Documentation
+----------------------
+Older rocm documentation is archived at https://rocmdocs.amd.com.
+
+# Disclaimer
+
+The information presented in this document is for informational purposes only and may contain technical inaccuracies, omissions, and typographical errors.  The information contained herein is subject to change and may be rendered inaccurate for many reasons, including but not limited to product and roadmap changes, component and motherboard versionchanges, new  model and/or product releases, product differences between differing manufacturers, software changes, BIOS flashes, firmware upgrades, or the like. Any computer system has risks of security vulnerabilities that cannot be completely prevented or mitigated.AMD  assumes  no  obligation  to  update  or  otherwise  correct  or  revise  this  information.  However, AMD reserves the right to revise this information and to make changes from time to time to the content hereof without obligation of AMD to notify any person of such revisions or changes.THIS INFORMATION IS PROVIDED ‘AS IS.” AMD MAKES NO REPRESENTATIONS OR WARRANTIES WITH RESPECT  TO  THE  CONTENTS  HEREOF  AND  ASSUMES  NO  RESPONSIBILITY  FOR  ANY  INACCURACIES, ERRORS, OR OMISSIONS THAT MAY APPEAR IN THIS INFORMATION. AMD SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE.  IN NO EVENT WILL AMD BE LIABLE TO ANY PERSON FOR ANY RELIANCE, DIRECT, INDIRECT, SPECIAL,  OR  OTHER  CONSEQUENTIAL  DAMAGES  ARISING  FROM  THE  USE  OF  ANY  INFORMATION CONTAINED HEREIN, EVEN IF AMD IS EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.AMD,  the  AMD  Arrow  logo, and combinations thereof are trademarks of Advanced Micro Devices, Inc.Other product names  used  in  this  publication  are  for  identification  purposes  only  and  may  be  trademarks  of  their respective  companies.
+©[2021]Advanced Micro Devices, Inc.All rights reserved.
+
+## Third-party Disclaimer
+Third-party content is licensed to you directly by the third party that owns the content and is not licensed to you by AMD.  ALL LINKED THIRD-PARTY CONTENT IS PROVIDED “AS IS” WITHOUT A WARRANTY OF ANY KIND.  USE OF SUCH THIRD-PARTY CONTENT IS DONE AT YOUR SOLE DISCRETION AND UNDER NO CIRCUMSTANCES WILL AMD BE LIABLE TO YOU FOR ANY THIRD-PARTY CONTENT.  YOU ASSUME ALL RISK AND ARE SOLELY RESPONSIBLE FOR ANY DAMAGES THAT MAY ARISE FROM YOUR USE OF THIRD-PARTY CONTENT. 

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2022 Advanced Micro Devices, Inc. All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -1,688 +1,93 @@
-## Are You Ready to ROCK?
-The ROCm Platform brings a rich foundation to advanced computing by seamlessly integrating the CPU and GPU with the goal of solving real-world problems.
-This software enables the high-performance operation of AMD GPUs for computationally oriented tasks in the Linux operating system.
+# ROCm™ Repository Updates
+This repository contains the manifest file for ROCm™ releases, changelogs, and release information. The file default.xml contains information for all repositories and the associated commit used to build the current ROCm release.
 
-### Current ROCm Version: 2.4
+The default.xml file uses the repo Manifest format.
 
-- [New features and enhancements in ROCm 2.4](#new-features-and-enhancements-in-rocm-24)
-- [The latest ROCm platform - ROCm 2.4](#the-latest-rocm-platform---rocm-240)
-- [Hardware Support](#hardware-support)
-  * [Supported GPUs](#supported-gpus)
-  * [Supported CPUs](#supported-cpus)
-  * [Not supported or limited support under ROCm](#not-supported-or-limited-support-under-rocm)
-- [Supported Operating Systems](#supported-operating-systems---new-operating-systems-available)
-  * [ROCm support in upstream Linux kernels](#rocm-support-in-upstream-linux-kernels)
-- [Installing from AMD ROCm repositories](#installing-from-amd-rocm-repositories)
-  * [ROCm Binary Package Structure](#rocm-binary-package-structure)
-  * [Ubuntu Support - installing from a Debian repository](#ubuntu-support---installing-from-a-debian-repository)
-  * [CentOS/RHEL 7 (7.4, 7.5, 7.6) Support](#centosrhel-7-74-75-76-support)
-- [Known issues / workarounds](#known-issues--workarounds)
-- [Closed source components](#closed-source-components)
-- [Getting ROCm source code](#getting-rocm-source-code)
-  * [Installing repo](#installing-repo)
-  * [Downloading the ROCm source code](#downloading-the-rocm-source-code)
-  * [Building the ROCm source code](#building-the-rocm-source-code)
-- [Deprecation Notice](#deprecation-notice)
-- [Final notes](#final-notes)
+# ROCm v5.4.1 Release Notes
+ROCm v5.4.1 is now released. For ROCm v5.4.1 documentation, refer to https://docs.amd.com.
 
-### New features and enhancements in ROCm 2.4
+# ROCm v5.4 Release Notes
+ROCm v5.4 is now released. For ROCm v5.4 documentation, refer to https://docs.amd.com.
 
-#### TensorFlow 2.0 support
-ROCm 2.4 includes the enhanced compilation toolchain and a set of bug fixes to support TensorFlow 2.0 features natively
+# ROCm v5.3.3 Release Notes
+ROCm v5.3.3 is now released. For ROCm v5.3.3 documentation, refer to https://docs.amd.com.
 
-#### AMD Infinity Fabric™ Link enablement 
-ROCm 2.4 adds support to connect two Radeon Instinct MI60 or Radeon Instinct MI50 boards via AMD Infinity Fabric™ Link GPU interconnect technology.
+# ROCm v5.3.2 Release Notes
+ROCm v5.3.2 is now released. For ROCm v5.3.2 documentation, refer to https://docs.amd.com.
 
-Features and enhancements introduced in previous versions of ROCm can be found in [version_history.md](version_history.md)
+# ROCm v5.3 Release Notes
+ROCm v5.3 is now released. For ROCm v5.3 documentation, refer to https://docs.amd.com.
 
-### The latest ROCm platform - ROCm 2.4
+# ROCm v5.2.3 Release Notes
+The ROCm v5.2.3 patch release is now available. The details are listed below. Highlights of this release include enhancements in RCCL version compatibility and minor bug fixes in the HIP Runtime.
 
-The latest supported version of the drivers, tools, libraries and source code for the ROCm platform have been released and are available from the following GitHub repositories:
+Additionally, ROCm releases will return to use of the [ROCm](https://github.com/RadeonOpenCompute/ROCm) repository for version-controlled release notes henceforth.
 
-* ROCm Core Components
-  - [ROCk Kernel Driver](https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/tree/roc-2.4.0)
-  - [ROCr Runtime](https://github.com/RadeonOpenCompute/ROCR-Runtime/tree/84443a1)
-  - [ROCt Thunk Interface](https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface/tree/roc-2.4.0)
-* ROCm Support Software
-  - [ROCm SMI](https://github.com/RadeonOpenCompute/ROC-smi/tree/roc-2.4.0)
-  - [ROCm cmake](https://github.com/RadeonOpenCompute/rocm-cmake/tree/ac45c6e2)
-  - [rocminfo](https://github.com/RadeonOpenCompute/rocminfo/tree/d34b716a)
-  - [ROCm Bandwidth Test](https://github.com/RadeonOpenCompute/rocm_bandwidth_test/tree/fe64704a)
-* ROCm Development Tools
-  - [HCC compiler](https://github.com/RadeonOpenCompute/hcc/tree/roc-2.4.0)
-  - [HIP](https://github.com/ROCm-Developer-Tools/HIP/tree/roc-2.4.0)
-  - [ROCm Device Libraries](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/roc-2.4.0)
-  - ROCm OpenCL, which is created from the following components:
-    - [ROCm OpenCL Runtime](http://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime/tree/roc-2.4.0)
-    - [ROCm OpenCL Driver](http://github.com/RadeonOpenCompute/ROCm-OpenCL-Driver/tree/roc-2.4.0)
-    - The ROCm OpenCL compiler, which is created from the following components:
-      - [ROCm LLVM OCL](http://github.com/RadeonOpenCompute/llvm/tree/roc-ocl-2.4.0)
-      - [ROCm LLVM HCC](http://github.com/RadeonOpenCompute/llvm/tree/roc-hcc-2.4.0)
-      - [ROCm Clang](http://github.com/RadeonOpenCompute/clang/tree/roc-2.4.0)
-      - [ROCm lld OCL](http://github.com/RadeonOpenCompute/lld/tree/roc-ocl-2.4.0)
-      - [ROCm lld HCC](http://github.com/RadeonOpenCompute/lld/tree/roc-hcc-2.4.0)
-      - [ROCm Device Libraries](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/roc-2.4.0)
-  - [ROCM Clang-OCL Kernel Compiler](https://github.com/RadeonOpenCompute/clang-ocl/tree/roc-2.4.0)
-  - [Asynchronous Task and Memory Interface (ATMI)](https://github.com/RadeonOpenCompute/atmi/tree/4dd14ad8)
-  - [ROCr Debug Agent](https://github.com/ROCm-Developer-Tools/rocr_debug_agent/tree/roc-2.4.0)
-  - [ROCm Code Object Manager](https://github.com/RadeonOpenCompute/ROCm-CompilerSupport/tree/roc-2.4.0)
-  - [ROC Profiler](https://github.com/ROCm-Developer-Tools/rocprofiler/tree/roc-2.4.x)
-  - [ROC Tracer](https://github.com/ROCm-Developer-Tools/roctracer/tree/roc-2.4.x)
-  - [Radeon Compute Profiler](https://github.com/GPUOpen-Tools/RCP/tree/a31fe682)
-  - Example Applications:
-    - [HCC Examples](https://github.com/ROCm-Developer-Tools/HCC-Example-Application/tree/ffd65333)
-    - [HIP Examples](https://github.com/ROCm-Developer-Tools/HIP-Examples/tree/roc-2.4.0)
-* ROCm Libraries
-  - [rocBLAS](https://github.com/ROCmSoftwarePlatform/rocBLAS/tree/master-rocm-2.4)
-  - [hipBLAS](https://github.com/ROCmSoftwarePlatform/hipBLAS/tree/master-rocm-2.4)
-  - [rocFFT](https://github.com/ROCmSoftwarePlatform/rocFFT/tree/master-rocm-2.4)
-  - [rocRAND](https://github.com/ROCmSoftwarePlatform/rocRAND/tree/master-rocm-2.4)
-  - [rocSPARSE](https://github.com/ROCmSoftwarePlatform/rocSPARSE/tree/master-rocm-2.4)
-  - [hipSPARSE](https://github.com/ROCmSoftwarePlatform/hipSPARSE/tree/master-rocm-2.4)
-  - [rocALUTION](https://github.com/ROCmSoftwarePlatform/rocALUTION/tree/master-rocm-2.4)
-  - [MIOpenGEMM](https://github.com/ROCmSoftwarePlatform/MIOpenGEMM/tree/9547fb9e)
-  - [MIOpen](https://github.com/ROCmSoftwarePlatform/MIOpen/tree/9fb1826d)
-  - [HIP Thrust](https://github.com/ROCmSoftwarePlatform/Thrust/tree/master-rocm-2.4)
-  - [ROCm SMI Lib](https://github.com/RadeonOpenCompute/rocm_smi_lib/tree/roc-2.4.0)
-  - [RCCL](https://github.com/ROCmSoftwarePlatform/rccl/tree/master-rocm-2.4)
-  - [MIVisionX](https://github.com/GPUOpen-ProfessionalCompute-Libraries/MIVisionX/tree/f05574dc)
-  - [CUB HIP](https://github.com/ROCmSoftwarePlatform/cub-hip/tree/hip_port_1.7.4)
+**NOTE**: This release of ROCm is validated with the AMDGPU release v22.20.1.
 
-### Hardware Support
-ROCm is focused on using AMD GPUs to accelerate computational tasks such as machine learning, engineering workloads, and scientific computing.
-In order to focus our development efforts on these domains of interest, ROCm supports a targeted set of hardware configurations which are detailed further in this section.
-
-#### Supported GPUs
-Because the ROCm Platform has a focus on particular computational domains, we offer official support for a selection of AMD GPUs that are designed to offer good performance and price in these domains.
-
-ROCm officially supports AMD GPUs that use following chips:
-
-  * GFX8 GPUs
-    * "Fiji" chips, such as on the AMD Radeon R9 Fury X and Radeon Instinct MI8
-    * "Polaris 10" chips, such as on the AMD Radeon RX 580 and Radeon Instinct MI6
-    * "Polaris 11" chips, such as on the AMD Radeon RX 570 and Radeon Pro WX 4100
-    * "Polaris 12" chips, such as on the AMD Radeon RX 550 and Radeon RX 540
-  * GFX9 GPUs
-    * "Vega 10" chips, such as on the AMD Radeon RX Vega 64 and Radeon Instinct MI25
-    * "Vega 7nm" chips, such as on the Radeon Instinct MI50, Radeon Instinct MI60 or AMD Radeon VII
-
-ROCm is a collection of software ranging from drivers and runtimes to libraries and developer tools.
-Some of this software may work with more GPUs than the "officially supported" list above, though AMD does not make any official claims of support for these devices on the ROCm software platform.
-The following list of GPUs are enabled in the ROCm software, though full support is not guaranteed:
-
-  * GFX7 GPUs
-    * "Hawaii" chips, such as the AMD Radeon R9 390X and FirePro W9100
-
-As described in the next section, GFX8 GPUs require PCI Express 3.0 (PCIe 3.0) with support for PCIe atomics. This requires both CPU and motherboard support. GFX9 GPUs, by default, also require PCIe 3.0 with support for PCIe atomics, but they can operate in most cases without this capability.
-
-At this time, the integrated GPUs in AMD APUs are not officially supported targets for ROCm.
-As descried [below](#limited-support), "Carrizo", "Bristol Ridge", and "Raven Ridge" APUs are enabled in our upstream drivers and the ROCm OpenCL runtime.
-However, they are not enabled in our HCC or HIP runtimes, and may not work due to motherboard or OEM hardware limitations.
-As such, they are not yet officially supported targets for ROCm.
-
-For a more detailed list of hardware support, please see [the following documentation](https://rocm.github.io/hardware.html).
-
-#### Supported CPUs
-As described above, GFX8 GPUs require PCIe 3.0 with PCIe atomics in order to run ROCm.
-In particular, the CPU and every active PCIe point between the CPU and GPU require support for PCIe 3.0 and PCIe atomics.
-The CPU root must indicate PCIe AtomicOp Completion capabilities and any intermediate switch must indicate PCIe AtomicOp Routing capabilities.
-
-Current CPUs which support PCIe Gen3 + PCIe Atomics are:
-
-  * AMD Ryzen CPUs;
-  * The CPUs in AMD Ryzen APUs;
-  * AMD Ryzen Threadripper CPUs
-  * AMD EPYC CPUs;  
-  * Intel Xeon E7 v3 or newer CPUs;
-  * Intel Xeon E5 v3 or newer CPUs; 
-  * Intel Xeon E3 v3 or newer CPUs;
-  * Intel Core i7 v4, Core i5 v4, Core i3 v4 or newer CPUs (i.e. Haswell family or newer).
-  * Some Ivy Bridge-E systems
-
-Beginning with ROCm 1.8, GFX9 GPUs (such as Vega 10) no longer require PCIe atomics.
-We have similarly opened up more options for number of PCIe lanes.
-GFX9 GPUs can now be run on CPUs without PCIe atomics and on older PCIe generations, such as PCIe 2.0.
-This is not supported on GPUs below GFX9, e.g. GFX8 cards in the Fiji and Polaris families.
-
-If you are using any PCIe switches in your system, please note that PCIe Atomics are only supported on some switches, such as Broadcom PLX.
-When you install your GPUs, make sure you install them in a PCIe 3.0 x16, x8, x4, or x1 slot attached either directly to the CPU's Root I/O controller or via a PCIe switch directly attached to the CPU's Root I/O controller.
-
-In our experience, many issues stem from trying to use consumer motherboards which provide physical x16 connectors that are electrically connected as e.g. PCIe 2.0 x4, PCIe slots connected via the Southbridge PCIe I/O controller, or PCIe slots connected through a PCIe switch that does
-not support PCIe atomics.
-
-If you attempt to run ROCm on a system without proper PCIe atomic support, you may see an error in the kernel log (`dmesg`):
-```
-kfd: skipped device 1002:7300, PCI rejects atomics
-```
-
-Experimental support for our Hawaii (GFX7) GPUs (Radeon R9 290, R9 390, FirePro W9100, S9150, S9170)
-does not require or take advantage of PCIe Atomics. However, we still recommend that you use a CPU
-from the list provided above for compatibility purposes.
-
-#### Not supported or limited support under ROCm 
-##### Limited support 
-
-* ROCm 2.4.x should support PCIe 2.0 enabled CPUs such as the AMD Opteron, Phenom, Phenom II, Athlon, Athlon X2, Athlon II and older Intel Xeon and Intel Core Architecture and Pentium CPUs. However, we have done very limited testing on these configurations, since our test farm has been catering to CPUs listed above. This is where we need community support. _If you find problems on such setups, please report these issues_.
-* Thunderbolt 1, 2, and 3 enabled breakout boxes should now be able to work with ROCm. Thunderbolt 1 and 2 are PCIe 2.0 based, and thus are only supported with GPUs that do not require PCIe 3.0 atomics (e.g. Vega 10). However, we have done no testing on this configuration and would need community support due to limited access to this type of equipment.
-* AMD "Carrizo" and "Bristol Ridge" APUs are enabled to run OpenCL, but do not yet support HCC, HIP, or our libraries built on top of these compilers and runtimes.
-  * As of ROCm 2.1, "Carrizo" and "Bristol Ridge" require the use of upstream kernel drivers.
-  * In addition, various "Carrizo" and "Bristol Ridge" platforms may not work due to OEM and ODM choices when it comes to key configurations parameters such as inclusion of the required CRAT tables and IOMMU configuration parameters in the system BIOS.
-  * Before purchasing such a system for ROCm, please verify that the BIOS provides an option for enabling IOMMUv2 and that the system BIOS properly exposes the correct CRAT table. Inquire with your vendor about the latter.
-* AMD "Raven Ridge" APUs are enabled to run OpenCL, but do not yet support HCC, HIP, or our libraries built on top of these compilers and runtimes.
-  * As of ROCm 2.1, "Raven Ridge" requires the use of upstream kernel drivers.
-  * In addition, various "Raven Ridge" platforms may not work due to OEM and ODM choices when it comes to key configurations parameters such as inclusion of the required CRAT tables and IOMMU configuration parameters in the system BIOS.
-  * Before purchasing such a system for ROCm, please verify that the BIOS provides an option for enabling IOMMUv2 and that the system BIOS properly exposes the correct CRAT table. Inquire with your vendor about the latter.
-  
-##### Not supported 
-
-* "Tonga", "Iceland", "Vega M", and "Vega 12" GPUs are not supported in ROCm 2.4.x
-* We do not support GFX8-class GPUs (Fiji, Polaris, etc.) on CPUs that do not have PCIe 3.0 with PCIe atomics.
-  * As such, we do not support AMD Carrizo and Kaveri APUs as hosts for such GPUs.
-  * Thunderbolt 1 and 2 enabled GPUs are not supported by GFX8 GPUs on ROCm. Thunderbolt 1 & 2 are based on PCIe 2.0.
-
-### Supported Operating Systems - New operating systems available
-
-The ROCm 2.4.x platform supports the following operating systems:
-
- * Ubuntu 16.04.x, 18.04.1 and 18.04.2 (Version 16.04.3 and newer or kernels 4.13-4.15)
- * CentOS 7.4, 7.5, and 7.6 (Using devtoolset-7 runtime support)
- * RHEL 7.4, 7.5, and 7.6 (Using devtoolset-7 runtime support)
-
-#### ROCm support in upstream Linux kernels
-
-As of ROCm 1.9.0, the ROCm user-level software is compatible with the AMD drivers in certain upstream Linux kernels.
-As such, users have the option of either using the ROCK kernel driver that are part of AMD's ROCm repositories or using the upstream driver and only installing ROCm user-level utilities from AMD's ROCm repositories.
-
-These releases of the upstream Linux kernel support the following GPUs in ROCm:
- * 4.17: Fiji, Polaris 10, Polaris 11
- * 4.18: Fiji, Polaris 10, Polaris 11, Vega10
- * 4.20: Fiji, Polaris 10, Polaris 11, Vega10, Vega 7nm
-
-The upstream driver may be useful for running ROCm software on systems that are not compatible with the kernel driver available in AMD's repositories.
-For users that have the option of using either AMD's or the upstreamed driver, there are various tradeoffs to take into consideration:
-
-|   | Using AMD's `rock-dkms` package | Using the upstream kernel driver |
-| ---- | ------------------------------------------------------------| ----- |
-| Pros | More GPU features, and they are enabled earlier | Includes the latest Linux kernel features |
-|      | Tested by AMD on supported distributions | May work on other distributions and with custom kernels |
-|      | Supported GPUs enabled regardless of kernel version | |
-|      | Includes the latest GPU firmware | |
-| Cons | May not work on all Linux distributions or versions | Features and hardware support varies depending on kernel version |
-|      | Not currently supported on kernels newer than 4.18 | Limits GPU's usage of system memory to 3/8 of system memory |
-|      |   | IPC and RDMA capabilities are not yet enabled |
-|      |   | Not tested by AMD to the same level as `rock-dkms` package |
-|      |   | Does not include most up-to-date firmware |
+All users of the ROCm v5.2.1 release and below are encouraged to upgrade. Refer to https://docs.amd.com for documentation associated with this release.
 
 
-### Installing from AMD ROCm repositories
+## Introducing Preview Support for Ubuntu 20.04.5 HWE
 
-AMD hosts both [Debian](http://repo.radeon.com/rocm/apt/debian/) and [RPM](http://repo.radeon.com/rocm/yum/rpm/) repositories for the ROCm 2.4.x packages at this time.
+Refer to the following article for information on the preview support for Ubuntu 20.04.5 HWE.
 
-The packages in the Debian repository have been signed to ensure package integrity.
+https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-22-20
 
-#### ROCm Binary Package Structure
 
-ROCm is a collection of software ranging from drivers and runtimes to libraries and developer tools.
-In AMD's package distributions, these software projects are provided as a separate packages.
-This allows users to install only the packages they need, if they do not wish to install all of ROCm.
-These packages will install most of the ROCm software into `/opt/rocm/` by default.
+## Changes in This Release
 
-The packages for each of the major ROCm components are:
+### Ubuntu 18.04 End of Life
 
-* ROCm Core Components
-  - ROCk Kernel Driver: `rock-dkms`
-  - ROCr Runtime: `hsa-rocr-dev`, `hsa-ext-rocr-dev`
-  - ROCt Thunk Interface: `hsakmt-roct`, `hsakmt-roct-dev`
-* ROCm Support Software
-  - ROCm SMI: `rocm-smi`
-  - ROCm cmake: `rocm-cmake`
-  - rocminfo: `rocminfo`
-  - ROCm Bandwidth Test: `rocm_bandwidth_test`
-* ROCm Development Tools
-  - HCC compiler: `hcc`
-  - HIP: `hip_base`, `hip_doc`, `hip_hcc`, `hip_samples`
-  - ROCm Device Libraries: `rocm-device-libs`
-  - ROCm OpenCL: `rocm-opencl`, `rocm-opencl-devel` (on RHEL/CentOS), `rocm-opencl-dev` (on Ubuntu)
-  - ROCM Clang-OCL Kernel Compiler: `rocm-clang-ocl`
-  - Asynchronous Task and Memory Interface (ATMI): `atmi`
-  - ROCr Debug Agent: `rocr_debug_agent`
-  - ROCm Code Object Manager: `comgr`
-  - ROC Profiler: `rocprofiler-dev`
-  - ROC Tracer: `roctracer-dev`
-  - Radeon Compute Profiler: `rocm-profiler`
-* ROCm Libraries
-  - rocBLAS: `rocblas`
-  - hipBLAS: `hipblas`
-  - rocFFT: `rocfft`
-  - rocRAND: `rocrand`
-  - rocSPARSE: `rocsparse`
-  - hipSPARSE: `hipsparse`
-  - rocALUTION: `rocalution:`
-  - MIOpenGEMM: `miopengemm`
-  - MIOpen: `MIOpen-HIP` (for the HIP version), `MIOpen-OpenCL` (for the OpenCL version)
-  - HIP Thrust: `thrust` (on RHEL/CentOS), `hip-thrust` (on Ubuntu)
-  - ROCm SMI Lib: `rocm_smi_lib64`
-  - RCCL: `rccl`
-  - MIVisionX: `mivisionx`
-  - CUB HIP: `cub-hip`
+Support for Ubuntu 18.04 ends in this release. Future releases of ROCm will not provide prebuilt packages for Ubuntu 18.04.
 
-To make it easier to install ROCm, the AMD binary repos provide a number of meta-packages that will automatically install multiple other packages.
-For example, `rocm-dkms` is the primary meta-package that is used to install most of the base technology needed for ROCm to operate.
-It will install the `rock-dkms` kernel driver, and another meta-package (`rocm-dev`) which installs most of the user-land ROCm core components, support software, and development tools.
 
-The `rocm-utils` meta-package will install useful utilities that, while not required for ROCm to operate, may still be beneficial to have.
-Finally, the `rocm-libs` meta-package will install some (but not all) of the libraries that are part of ROCm.
+### HIP and Other Runtimes
 
-The chain of software installed by these meta-packages is illustrated below
+#### HIP Runtime
+
+##### Fixes
+
+ - A bug was discovered in the HIP graph capture implementation in the ROCm v5.2.0 release. If the same kernel is called twice (with different argument values) in a graph capture, the implementation only kept the argument values for the second kernel call.
+
+- A bug was introduced in the hiprtc implementation in the ROCm v5.2.0 release. This bug caused the *hiprtcGetLoweredName* call to fail for named expressions with whitespace in it.
+
+**Example:** The named expression ```my_sqrt<complex<double>>``` passed but ```my_sqrt<complex<double>>``` failed.
+
+
+### ROCm Libraries
+
+#### RCCL
+
+##### Added
+- Compatibility with NCCL 2.12.10
+- Packages for test and benchmark executables on all supported OSes using CPack
+- Adding custom signal handler - opt-in with RCCL_ENABLE_SIGNALHANDLER=1
+  - Additional details provided if Binary File Descriptor library (BFD) is pre-installed.
+  - Adding experimental support for using multiple ranks per device
+    - Requires using a new interface to create communicator (ncclCommInitRankMulti),
+        refer to the interface documentation for details.
+	  - To avoid potential deadlocks, user might have to set an environment variables increasing
+	      the number of hardware queues. For example,
 
 ```
-rocm-dkms
- |-- rock-dkms
- \-- rocm-dev
-      |--hsa-rocr-dev
-      |--hsa-ext-rocr-dev
-      |--rocm-device-libs
-      |--rocm-utils
-          |-- rocminfo
-          |-- rocm-cmake
-          \-- rocm-clang-ocl # This will cause OpenCL to be installed
-      |--hcc
-      |--hip_base
-      |--hip_doc
-      |--hip_hcc
-      |--hip_samples
-      |--rocm-smi
-      |--hsakmt-roct
-      |--hsakmt-roct-dev
-      |--hsa-amd-aqlprofile
-      |--comgr
-      \--rocr_debug_agent
+    export GPU_MAX_HW_QUEUES=16
 
-rocm-libs
- |-- rocblas
- |-- rocfft
- |-- rocrand
- \-- hipblas
 ```
+- Adding support for reusing ports in NET/IB channels
+  - Opt-in with NCCL_IB_SOCK_CLIENT_PORT_REUSE=1 and NCCL_IB_SOCK_SERVER_PORT_REUSE=1
+    - When "Call to bind failed: Address already in use" error happens in large-scale AlltoAll
+        (for example, >=64 MI200 nodes), users are suggested to opt-in either one or both of the options to resolve the massive port usage issue
+	  - Avoid using NCCL_IB_SOCK_SERVER_PORT_REUSE when NCCL_NCHANNELS_PER_NET_PEER is tuned >1
 
-These meta-packages are not required but may be useful to make it easier to install ROCm on most systems.
-Some users may want to skip certain packages. For instance, a user that wants to use the upstream kernel drivers (rather than those supplied by AMD) may want to skip the `rocm-dkms` and `rock-dkms` packages, and instead directly install `rocm-dev`.
+##### Removed
+- Removed experimental clique-based kernels
 
-Similarly, a user that only wants to install OpenCL support instead of HCC and HIP may want to skip the `rocm-dkms` and `rocm-dev` packages.
-Instead, they could directly install `rock-dkms`, `rocm-opencl`, and `rocm-opencl-dev` and their dependencies.
+### Development Tools
+No notable changes in this release for development tools, including the compiler, profiler, and debugger.
 
-#### Ubuntu Support - installing from a Debian repository
+### Deployment and Management Tools
+No notable changes in this release for deployment and management tools.
 
-The following directions show how to install ROCm on supported Debian-based systems such as Ubuntu 18.04.
-These directions may not work as written on unsupported Debian-based distributions.
-For example, newer versions of Ubuntu may not be compatible with the `rock-dkms` kernel driver.
-As such, users may want to skip the `rocm-dkms` and `rock-dkms` packages, as described [above](#rocm-binary-package-structure), and instead [use the upstream kernel driver](#using-debian-based-rocm-with-upstream-kernel-drivers).
-
-##### First make sure your system is up to date 
-
-```shell
-sudo apt update
-sudo apt dist-upgrade
-sudo apt install libnuma-dev
-sudo reboot
-```
-
-##### Add the ROCm apt repository
-
-For Debian-based systems like Ubuntu, configure the Debian ROCm repository as
-follows:
-
-```shell
-wget -qO - http://repo.radeon.com/rocm/apt/debian/rocm.gpg.key | sudo apt-key add -
-echo 'deb [arch=amd64] http://repo.radeon.com/rocm/apt/debian/ xenial main' | sudo tee /etc/apt/sources.list.d/rocm.list
-```
-The gpg key might change, so it may need to be updated when installing a new release. 
-If the key signature verification is failed while update, please re-add the key from 
-ROCm apt repository. The current rocm.gpg.key is not available in a standard key ring 
-distribution, but has the following sha1sum hash:
-
-`f7f8147431c75e505c58a6f3a3548510869357a6  rocm.gpg.key`
-
-##### Install
-
-Next, update the apt repository list and install the `rocm-dkms` meta-package:
-
-```shell
-sudo apt update
-sudo apt install rocm-dkms
-```
-
-##### Next set your permissions 
-
-Users will need to be in the `video` group in order to have access to the GPU.
-As such, you should ensure that your user account is a member of the `video` group prior to using ROCm.
-You can find which groups you are a member of with the following command:
-
-```shell
-groups
-```
-
-To add yourself to the video group you will need the sudo password and can use the following command:
-
-```shell
-sudo usermod -a -G video $LOGNAME 
-```
-
-You may want to ensure that any future users you add to your system are put into the "video" group by default. To do that, you can run the following commands:
-
-```shell
-echo 'ADD_EXTRA_GROUPS=1' | sudo tee -a /etc/adduser.conf
-echo 'EXTRA_GROUPS=video' | sudo tee -a /etc/adduser.conf
-```
-
-Once complete, reboot your system.
-
-##### Test basic ROCm installation
-
-After rebooting the system run the following commands to verify that the ROCm installation was successful. If you see your GPUs listed by both of these commands, you should be ready to go!
-
-```shell
-/opt/rocm/bin/rocminfo 
-/opt/rocm/opencl/bin/x86_64/clinfo 
-```
-
-Note that, to make running ROCm programs easier, you may wish to put the ROCm binaries in your PATH.
-
-```shell
-echo 'export PATH=$PATH:/opt/rocm/bin:/opt/rocm/profiler/bin:/opt/rocm/opencl/bin/x86_64' | sudo tee -a /etc/profile.d/rocm.sh
-```
-
-If you have an [install issue](https://rocm.github.io/install_issues.html) please read this FAQ.
-
-##### Performing an OpenCL-only Installation of ROCm
-
-Some users may want to install a subset of the full ROCm installation.
-In particular, if you are trying to install on a system with a limited amount of storage space, or which will only run a small collection of known applications, you may want to install only the packages that are required to run OpenCL applications.
-To do that, you can run the following installation command **instead** of the command to install `rocm-dkms`.
-
-```shell
-sudo apt-get install dkms rock-dkms rocm-opencl-dev
-```
-
-##### How to uninstall from Ubuntu 16.04 or Ubuntu 18.04
-
-To uninstall the ROCm packages installed in the above directions, you can execute;
-
-```shell
-sudo apt autoremove rocm-dkms rocm-dev rocm-utils
-```
-
-##### Installing development packages for cross compilation
-
-It is often useful to develop and test on different systems.
-For example, some development or build systems may not have an AMD GPU installed.
-In this scenario, you may prefer to avoid installing the ROCK kernel driver to your development system.
-
-In this case, install the development subset of packages:
-
-```shell
-sudo apt update
-sudo apt install rocm-dev
-```
->**Note:** To execute ROCm enabled apps you will require a system with the full
->ROCm driver stack installed
-
-##### Using Debian-based ROCm with upstream kernel drivers
-
-As described in [the above section about upstream Linux kernel support](#rocm-support-in-upstream-linux-kernels), users may want to try installing ROCm user-level software without installing AMD's custom ROCK kernel driver.
-Users who do want to use upstream kernels can run the following commands instead of installing `rocm-dkms`
-
-```shell
-sudo apt update
-sudo apt install rocm-dev
-echo 'SUBSYSTEM=="kfd", KERNEL=="kfd", TAG+="uaccess", GROUP="video"' | sudo tee /etc/udev/rules.d/70-kfd.rules
-```
-
-#### CentOS/RHEL 7 (7.4, 7.5, 7.6) Support
-
-The following directions show how to install ROCm on supported RPM-based systems such as CentOS 7.6.
-These directions may not work as written on unsupported RPM-based distributions.
-For example, Fedora may work but may not be compatible with the `rock-dkms` kernel driver.
-As such, users may want to skip the `rocm-dkms` and `rock-dkms` packages, as described [above](#rocm-binary-package-structure), and instead [use the upstream kernel driver](#using-rpm-based-rocm-with-upstream-kernel-drivers).
-
-Support for CentOS/RHEL 7 was added in ROCm 1.8, but ROCm requires a special 
-runtime environment provided by the RHEL Software Collections and additional
-dkms support packages to properly install and run.
-
-##### Preparing RHEL 7 (7.4, 7.5, 7.6) for installation
-
-RHEL is a subscription-based operating system, and you must enable several external
-repositories to enable installation of the devtoolset-7 environment and the DKMS
-support files. These steps are not required for CentOS.
-
-First, the subscription for RHEL must be enabled and attached to a pool id. Please
-see Obtaining an RHEL image and license page for instructions on registering your
-system with the RHEL subscription server and attaching to a pool id.
-
-
-Second, enable the following repositories:
-
-```shell
-sudo subscription-manager repos --enable rhel-server-rhscl-7-rpms
-sudo subscription-manager repos --enable rhel-7-server-optional-rpms
-sudo subscription-manager repos --enable rhel-7-server-extras-rpms
-```
-
-Third, enable additional repositories by downloading and installing the epel-release-latest-7 repository RPM:
-
-```shell
-sudo rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-```
-
-##### Install and setup Devtoolset-7
-
-To setup the Devtoolset-7 environment, follow the instructions on this page:
-
-https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
-
-Note that devtoolset-7 is a Software Collections package, and it is not supported by AMD.
-
-##### Prepare CentOS/RHEL (7.4, 7.5, 7.6) for DKMS Install
-
-Installing kernel drivers on CentOS/RHEL 7.4/7.5/7.6 requires dkms tool being installed:
-
-```shell
-sudo yum install -y epel-release
-sudo yum install -y dkms kernel-headers-`uname -r` kernel-devel-`uname -r`
-```
-
-##### Installing ROCm on the system
-
-It is recommended to [remove previous ROCm installations](https://github.com/RadeonOpenCompute/ROCm#how-to-uninstall-rocm-from-centosrhel-74-75-and-76) before installing the latest version to ensure a smooth installation.
-
-At this point ROCm can be installed on the target system. Create a /etc/yum.repos.d/rocm.repo file with the following contents:
-
-```shell
-[ROCm]
-name=ROCm
-baseurl=http://repo.radeon.com/rocm/yum/rpm
-enabled=1
-gpgcheck=0
-```
-
-The repo's URL should point to the location of the repositories repodata database. Install ROCm components using these commands:
-
-```shell
-sudo yum install rocm-dkms
-```
-
-The rock-dkms component should be installed and the `/dev/kfd` device should be available on reboot.
-
-##### Set up permissions
-
-Ensure that your user account is a member of the "video" or "wheel" group prior to using the ROCm driver.
-You can find which groups you are a member of with the following command:
-
-```shell
-groups
-```
-
-To add yourself to the video (or wheel) group you will need the sudo password and can use the
-following command:
-
-```shell
-sudo usermod -a -G video $LOGNAME 
-```
-
-You may want to ensure that any future users you add to your system are put into the "video" group by default. To do that, you can run the following commands:
-
-```shell
-echo 'ADD_EXTRA_GROUPS=1' | sudo tee -a /etc/adduser.conf
-echo 'EXTRA_GROUPS=video' | sudo tee -a /etc/adduser.conf
-```
-
-Current release supports CentOS/RHEL 7.4, 7.5, 7.6. If users want to update the OS version, they should completely remove ROCm packages before updating to the latest version of the OS, to avoid DKMS related issues.
-
-Once complete, reboot your system.
-
-###### Test basic ROCm installation
-
-After rebooting the system run the following commands to verify that the ROCm installation was successful. If you see your GPUs listed by both of these commands, you should be ready to go!
-
-```shell
-/opt/rocm/bin/rocminfo
-/opt/rocm/opencl/bin/x86_64/clinfo
-```
-
-Note that, to make running ROCm programs easier, you may wish to put the ROCm binaries in your PATH.
-
-```shell
-echo 'export PATH=$PATH:/opt/rocm/bin:/opt/rocm/profiler/bin:/opt/rocm/opencl/bin/x86_64' | sudo tee -a /etc/profile.d/rocm.sh
-```
-
-If you have an [install issue](https://rocm.github.io/install_issues.html) please read this FAQ.
-
-###### Performing an OpenCL-only Installation of ROCm
-
-Some users may want to install a subset of the full ROCm installation.
-In particular, if you are trying to install on a system with a limited amount of storage space, or which will only run a small collection of known applications, you may want to install only the packages that are required to run OpenCL applications.
-To do that, you can run the following installation command **instead** of the command to install `rocm-dkms`.
-
-```shell
-sudo yum install rock-dkms rocm-opencl-devel
-```
-
-##### Compiling applications using HCC, HIP, and other ROCm software
-
-To compile applications or samples, please use gcc-7.2 provided by the devtoolset-7 environment.
-To do this, compile all applications after running this command: 
-
-```shell
-scl enable devtoolset-7 bash
-```
-##### How to uninstall ROCm from CentOS/RHEL 7.4, 7.5 and 7.6
-
-To uninstall the ROCm packages installed by the above directions, you can execute:
-
-```shell
-sudo yum autoremove rocm-dkms rock-dkms
-```
-
-##### Installing development packages for cross compilation
-
-It is often useful to develop and test on different systems.
-For example, some development or build systems may not have an AMD GPU installed.
-In this scenario, you may prefer to avoid installing the ROCK kernel driver to your development system.
-
-In this case, install the development subset of packages:
-
-```shell
-sudo yum install rocm-dev
-```
->**Note:** To execute ROCm enabled apps you will require a system with the full
->ROCm driver stack installed
-
-##### Using ROCm with upstream kernel drivers
-
-As described in [the above section about upstream Linux kernel support](#rocm-support-in-upstream-linux-kernels), use
-rs may want to try installing ROCm user-level software without installing AMD's custom ROCK kernel driver.
-Users who do want to use upstream kernels can run the following commands instead of installing `rocm-dkms`
-
-```shell
-sudo yum install rocm-dev
-echo 'SUBSYSTEM=="kfd", KERNEL=="kfd", TAG+="uaccess", GROUP="video"' | sudo tee /etc/udev/rules.d/70-kfd.rules
-```
-
-### Known issues / workarounds
-
-#### MIOpen
-MIOpen unit test will fail at test_conv with the following error message –
-Memory access fault by GPU node-2 (Agent handle: 0x1fc0a10) on address 0x7fd3c3600000. Reason: Page not present or supervisor privilege
-
-#### TensorFlow
-Observed memory access fault while running SAGAN TensorFlow model in Polaris based ASIC
-
-#### Vega7nm
-GPU reset is not currently supported with boards connected with AMD Infinity Fabric&#x2122; Link GPU interconnect technology.
-
-
-### Closed source components
-
-The ROCm platform relies on a few closed source components to provide functionality
-such as HSA image support. These components are only available through the ROCm
-repositories, and they will either be deprecated or become open source components in the
-future. These components are made available in the following packages:
-
-*  hsa-ext-rocr-dev
-
-### Getting ROCm source code
-
-ROCm is built from open source software.
-As such, it is possible to make modifications to the various components of ROCm by downloading the source code, making modifications to it, and rebuilding the components.
-The source code for ROCm components can be cloned from each of the GitHub repositories using git.
-In order to make it easier to download the correct versions of each of these tools, this ROCm repository contains a [repo](https://gerrit.googlesource.com/git-repo/) manifest file, [default.xml](default.xml).
-Interested users can thus use this manifest file to download the source code for all of the ROCm software.
-
-#### Installing repo
-
-Google's repo tool allows you to manage multiple git repositories simultaneously.
-You can install it by executing the following example commands:
-
-```shell
-mkdir -p ~/bin/
-curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
-chmod a+x ~/bin/repo
-```
-Note that you can choose a different folder to install repo into if you desire. `~/bin/` is simply used as an example.
-
-#### Downloading the ROCm source code
-
-The following example shows how to use the `repo` binary downloaded above to download all of the ROCm source code.
-If you chose a directory other than `~/bin/` to install `repo`, you should use that directory below.
-
-```shell
-mkdir -p ~/ROCm/
-cd ~/ROCm/
-~/bin/repo init -u https://github.com/RadeonOpenCompute/ROCm.git -b roc-2.4.0
-repo sync
-```
-
-This will cause repo to download all of the open source code associated with this ROCm release.
-You may want to ensure that you have ssh-keys configured on your machine for your GitHub ID.
-
-#### Building the ROCm source code
-
-Each ROCm component repository contains directions for building that component.
-As such, you should go to the repository you are interested in building to find how to build it.
-
-That said, AMD also offers [a project](https://github.com/RadeonOpenCompute/Experimental_ROC) that demonstrates how to download, build, package, and install ROCm software on various distributions.
-The scripts here may be useful for anyone looking to build ROCm components.
-
-### Deprecation Notice - HCC 
-AMD is deprecating HCC to put more focus on HIP development and on
-other languages supporting heterogeneous compute.  We will no longer
-develop any new feature in HCC and we will stop maintaining HCC after
-its final release, which is planned for June 2019.  If your
-application was developed with the hc C++ API, we would encourage you
-to transition it to other languages supported by AMD, such as HIP or
-OpenCL.  HIP and hc language share the same compiler technology, so
-many hc kernel language features (including inline assembly) are also
-available through the HIP compilation path.
-
-### Final notes
-* OpenCL Runtime and Compiler will be submitted to the Khronos Group for conformance testing prior to its final release.
+## Older ROCm™ Releases
+For release information for older ROCm™ releases, refer to [CHANGELOG](CHANGELOG.md).

default.xml

@@ -1,73 +1,78 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <manifest>
-
     <remote name="roc-github"
-            fetch="http://github.com/RadeonOpenCompute/" />
+fetch="https://github.com/RadeonOpenCompute/" />
     <remote name="rocm-devtools"
-            fetch="https://github.com/ROCm-Developer-Tools/" />
+fetch="https://github.com/ROCm-Developer-Tools/" />
     <remote name="rocm-swplat"
-            fetch="https://github.com/ROCmSoftwarePlatform/" />
+fetch="https://github.com/ROCmSoftwarePlatform/" />
     <remote name="gpuopen-libs"
-            fetch="https://github.com/GPUOpen-ProfessionalCompute-Libraries/" />
+fetch="https://github.com/GPUOpen-ProfessionalCompute-Libraries/" />
     <remote name="gpuopen-tools"
-            fetch="https://github.com/GPUOpen-Tools/" />
-
-    <default revision="refs/tags/roc-2.4.0"
-             remote="roc-github"
-             sync-c="true"
-             sync-j="4" />
-
+fetch="https://github.com/GPUOpen-Tools/" />
+    <remote name="KhronosGroup"
+fetch="https://github.com/KhronosGroup/" />
+    <default revision="refs/tags/rocm-5.4.1"
+     remote="roc-github"
+     sync-c="true"
+     sync-j="4" />
+<!--list of projects for ROCM-->
     <project name="ROCK-Kernel-Driver" />
     <project name="ROCT-Thunk-Interface" />
     <project name="ROCR-Runtime" />
-    <project name="ROC-smi" />
-    <project name="rocm-cmake" revision="ac45c6e269d1fd1dbd5dfc81cfe47a7452c96daf" />
-    <project name="rocminfo" revision="1bb0ccc731f772bb1a553e37b41d06eb0a684926" />
+    <project name="rocm_smi_lib" />
+    <project name="rocm-cmake" />
+    <project name="rocminfo" />
     <project name="rocprofiler" remote="rocm-devtools" />
     <project name="roctracer" remote="rocm-devtools" />
-    <!-- If you want to get the full OpenCL runtime, there is a separate repo
-         manifest that is more authoritative than the copy in this file. It can
-         be found at the following URL:
-         https://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime/blob/roc-2.0.0/opencl.xml -->
-    <remote name="KhronosGroup" fetch="https://github.com/KhronosGroup/" />
     <project name="ROCm-OpenCL-Runtime" />
-    <project path="ROCm-OpenCL-Runtime/compiler/driver" name="ROCm-OpenCL-Driver"/>
-    <project path="ROCm-OpenCL-Runtime/compiler/llvm" name="llvm" revision="refs/tags/roc-ocl-2.4.0" />
-    <project path="ROCm-OpenCL-Runtime/compiler/llvm/tools/clang" name="clang" />
-    <project path="ROCm-OpenCL-Runtime/compiler/llvm/tools/lld" name="lld" revision="refs/tags/roc-ocl-2.4.0" />
-    <project path="ROCm-OpenCL-Runtime/library/amdgcn" name="ROCm-Device-Libs"/>
-    <project path="ROCm-OpenCL-Runtime/api/opencl/khronos/icd" name="OpenCL-ICD-Loader" remote="KhronosGroup" revision="261c1288aadd9dcc4637aca08332f603e6c13715" />
-
+    <project path="ROCm-OpenCL-Runtime/api/opencl/khronos/icd" name="OpenCL-ICD-Loader" remote="KhronosGroup" revision="6c03f8b58fafd9dd693eaac826749a5cfad515f8" />
     <project name="clang-ocl" />
-    <!-- HCC needs to be recursively synced to get it submodules -->
-    <project name="hcc" sync-s="true" />
-    <project name="HCC-Example-Application" remote="rocm-devtools" revision="ffd6533305e79eed667badd3c4cdb7879a1281b8" />
+<!--HIP Projects-->
     <project name="HIP" remote="rocm-devtools" />
+    <project name="hipamd" remote="rocm-devtools" />
     <project name="HIP-Examples" remote="rocm-devtools" />
-    <!-- The following projects are all associated with the AMDGPU LLVM compiler -->
-    <project name="llvm" path="llvm_amd-common" revision="refs/tags/roc-hcc-2.4.0" />
-    <project name="lld" path="llvm_amd-common/lld" revision="refs/tags/roc-hcc-2.4.0" />
-    <project name="clang" path="llvm_amd-common/clang" />
+    <project name="ROCclr" remote="rocm-devtools" />
+    <project name="HIPIFY" remote="rocm-devtools" />
+    <project name="HIPCC" remote="rocm-devtools" />
+<!-- The following projects are all associated with the AMDGPU LLVM compiler -->
+    <project name="llvm-project" />
     <project name="ROCm-Device-Libs" />
-    <project name="atmi" revision="4dd14ad8fafc64dc8f35b0646cfe84e3e36a3c64" />
+    <project name="atmi" />
     <project name="ROCm-CompilerSupport" />
     <project name="rocr_debug_agent" remote="rocm-devtools" />
     <project name="rocm_bandwidth_test" />
-    <project name="RCP" remote="gpuopen-tools" revision="refs/tags/v5.6" />
-
-    <!-- ROCm Libraries -->
-    <project name="rocBLAS" remote="rocm-swplat" revision="refs/tags/rocm-2.4" />
-    <project name="hipBLAS" remote="rocm-swplat" revision="refs/tags/rocm-2.4" />
-    <project name="rocFFT" remote="rocm-swplat" revision="9a0d296ce91889a4ac549adeac045604f040af92" />
-    <project name="rocRAND" remote="rocm-swplat" revision="687d659a294f416c69dd6e860a8ded939e55c22a" />
-    <project name="rocSPARSE" remote="rocm-swplat" revision="refs/tags/rocm-2.4" />
-    <project name="hipSPARSE" remote="rocm-swplat" revision="refs/tags/rocm-2.4" />
-    <project name="rocALUTION" remote="rocm-swplat" revision="refs/tags/rocm-2.4" />
-    <project name="MIOpenGEMM" remote="rocm-swplat" revision="9547fb9e8499a5a9f16da83b1e6b749de82dd9fb" />
-    <project name="MIOpen" remote="rocm-swplat" revision="refs/tags/roc-2.3.0" />
-    <project name="Thrust" remote="rocm-swplat" revision="a58d8d783c05202bd3fa7732c2af62362198112e" sync-s="true" />
-    <project name="rocm_smi_lib" />
-    <project name="rccl" remote="rocm-swplat" revision="refs/tags/0.7.5" />
-    <project name="MIVisionX" remote="gpuopen-libs" revision="f05574dc81b861cce7431153b9502718e79e0647" />
-    <project name="cub-hip" remote="rocm-swplat" revision="hip_port_1.7.4" />
+    <project name="half" remote="rocm-swplat" revision="37742ce15b76b44e4b271c1e66d13d2fa7bd003e" />
+    <project name="RCP" remote="gpuopen-tools" revision="3a49405a1500067c49d181844ec90aea606055bb" />
+<!-- gdb projects -->
+    <project name="ROCgdb" remote="rocm-devtools" />
+    <project name="ROCdbgapi" remote="rocm-devtools" />
+<!-- ROCm Libraries -->
+    <project name="rdc" />
+    <project name="rocBLAS" remote="rocm-swplat" />
+    <project name="Tensile" remote="rocm-swplat" />
+    <project name="hipBLAS" remote="rocm-swplat" />
+    <project name="rocFFT" remote="rocm-swplat" />
+    <project name="hipFFT" remote="rocm-swplat" />
+    <project name="rocRAND" remote="rocm-swplat" />
+    <project name="rocSPARSE" remote="rocm-swplat" />
+    <project name="rocSOLVER" remote="rocm-swplat" />
+    <project name="hipSOLVER" remote="rocm-swplat" />
+    <project name="hipSPARSE" remote="rocm-swplat" />
+    <project name="rocALUTION" remote="rocm-swplat" />
+    <project name="MIOpenGEMM" remote="rocm-swplat" />
+    <project name="MIOpen" remote="rocm-swplat" />
+    <project name="rccl" remote="rocm-swplat" />
+    <project name="MIVisionX" remote="gpuopen-libs" />
+    <project name="rocThrust" remote="rocm-swplat" />
+    <project name="hipCUB" remote="rocm-swplat" />
+    <project name="rocPRIM" remote="rocm-swplat" />
+    <project name="rocWMMA" remote="rocm-swplat" />
+    <project name="hipfort" remote="rocm-swplat" />
+    <project name="AMDMIGraphX" remote="rocm-swplat" />
+    <project name="ROCmValidationSuite" remote="rocm-devtools" />
+<!-- Projects for OpenMP-Extras -->
+    <project name="aomp" path="openmp-extras/aomp" remote="rocm-devtools" />
+    <project name="aomp-extras" path="openmp-extras/aomp-extras" remote="rocm-devtools" />
+    <project name="flang" path="openmp-extras/flang" remote="rocm-devtools" />
 </manifest>

version_history.md

@@ -1,257 +0,0 @@
-## ROCm Version History
-This file contains archived version history information for the [ROCm project](https://github.com/RadeonOpenCompute/ROCm)
-
-### Current ROCm Version: 2.4
-- [New features and enhancements in ROCm 2.3](#new-features-and-enhancements-in-rocm-23)
-- [New features and enhancements in ROCm 2.2](#new-features-and-enhancements-in-rocm-22)
-- [New features and enhancements in ROCm 2.1](#new-features-and-enhancements-in-rocm-21)
-- [New features and enhancements in ROCm 2.0](#new-features-and-enhancements-in-rocm-20)
-- [New features and enhancements in ROCm 1.9.2](#new-features-and-enhancements-in-rocm-192)
-- [New features and enhancements in ROCm 1.9.2](#new-features-and-enhancements-in-rocm-192-1)
-- [New features and enhancements in ROCm 1.9.1](#new-features-and-enhancements-in-rocm-191)
-- [New features and enhancements in ROCm 1.9.0](#new-features-and-enhancements-in-rocm-190)
-- [New features as of ROCm 1.8.3](#new-features-as-of-rocm-183)
-- [New features as of ROCm 1.8](#new-features-as-of-rocm-18)
-- [New Features as of ROCm 1.7](#new-features-as-of-rocm-17)
-- [New Features as of ROCm 1.5](#new-features-as-of-rocm-15)
-
-### New features and enhancements in ROCm 2.3
-
-#### Mem usage per GPU
-Per GPU memory usage is added to rocm-smi.
-Display information regarding used/total bytes for VRAM, visible VRAM and GTT, via the --showmeminfo flag
-
-#### MIVisionX, v1.1 - ONNX 
-ONNX parser changes to adjust to new file formats
-
-#### MIGraphX, v0.2
-MIGraphX 0.2 supports the following new features:
-* New Python API
-* Support for additional ONNX operators and fixes that now enable a large set of Imagenet models
-* Support for RNN Operators
-* Support for multi-stream Execution
-* [Experimental] Support for Tensorflow frozen protobuf files
-
-See: [Getting-started:-using-the-new-features-of-MIGraphX-0.2](https://github.com/ROCmSoftwarePlatform/AMDMIGraphX/wiki/Getting-started:-using-the-new-features-of-MIGraphX-0.2) for more details
-
-#### MIOpen, v1.8 - 3d convolutions and int8
-* This release contains full 3-D convolution support and int8 support for inference.
-* Additionally, there are major updates in the performance database for major models including those found in Torchvision.
-
-See: [MIOpen releases](https://github.com/ROCmSoftwarePlatform/MIOpen/releases)
-
-#### Caffe2 -  mGPU support 
-Multi-gpu support is enabled for Caffe2.
-
-#### rocTracer library, ROCm tracing API for collecting runtimes API and asynchronous GPU activity traces
-HIP/HCC domains support is introduced in rocTracer library.
-
-#### BLAS -  Int8 GEMM performance, Int8 functional and performance 
-Introduces support and performance optimizations for Int8 GEMM, implements TRSV support, and includes improvements and optimizations with Tensile.
-
-#### Prioritized L1/L2/L3 BLAS (functional) 
-Functional implementation of BLAS L1/L2/L3 functions
-
-#### BLAS - tensile optimization
-Improvements and optimizations with tensile
-
-#### MIOpen Int8 support
-Support for int8
-
-### New features and enhancements in ROCm 2.2
-
-#### rocSparse Optimization on Vega20
-Cache usage optimizations for csrsv (sparse triangular solve), coomv
-(SpMV in COO format) and ellmv (SpMV in ELL format) are available.
-
-#### DGEMM and DTRSM Optimization
-Improved DGEMM performance for reduced matrix sizes (k=384, k=256)
-
-#### Caffe2
-Added support for multi-GPU training
-
-### New features and enhancements in ROCm 2.1
-
-#### RocTracer v1.0 preview release – 'rocprof' HSA runtime tracing and statistics support -
-Supports HSA API tracing and HSA asynchronous GPU activity including kernels execution and memory copy
-     
-#### Improvements to ROCM-SMI tool -
-Added support to show real-time PCIe bandwidth usage via the -b/--showbw flag
-       
-#### DGEMM Optimizations -
-Improved DGEMM performance for large square and reduced matrix sizes (k=384, k=256)
-
-### New features and enhancements in ROCm 2.0
-
-#### Adds support for RHEL 7.6 / CentOS 7.6 and Ubuntu 18.04.1
-
-#### Adds support for Vega 7nm, Polaris 12 GPUs
-
-#### Introduces MIVisionX
-* A comprehensive computer vision and machine intelligence libraries, utilities and applications bundled into a single toolkit.
-
-#### Improvements to ROCm Libraries
-* rocSPARSE & hipSPARSE
-* rocBLAS with improved DGEMM efficiency on Vega 7nm
-
-#### MIOpen
-* This release contains general bug fixes and an updated performance database
-* Group convolutions backwards weights performance has been improved
-* RNNs now support fp16
-
-#### Tensorflow multi-gpu and Tensorflow FP16 support for Vega 7nm
-* TensorFlow v1.12 is enabled with fp16 support
-
-#### PyTorch/Caffe2 with Vega 7nm Support
-* fp16 support is enabled
-* Several bug fixes and performance enhancements
-* Known Issue: breaking changes are introduced in ROCm 2.0 which are not addressed upstream yet. Meanwhile, please continue to use ROCm fork at https://github.com/ROCmSoftwarePlatform/pytorch
-
-#### Improvements to ROCProfiler tool
-* Support for Vega 7nm
-
-#### Support for hipStreamCreateWithPriority
-* Creates a stream with the specified priority. It creates a stream on which enqueued kernels have a different priority for execution compared to kernels enqueued on normal priority streams. The priority could be higher or lower than normal priority streams.
-
-#### OpenCL 2.0 support
-* ROCm 2.0 introduces full support for kernels written in the OpenCL 2.0 C language on certain devices and systems.  Applications can detect this support by calling the “clGetDeviceInfo” query function with “parame_name” argument set to “CL_DEVICE_OPENCL_C_VERSION”.  In order to make use of OpenCL 2.0 C language features, the application must include the option “-cl-std=CL2.0” in options passed to the runtime API calls responsible for compiling or building device programs.  The complete specification for the OpenCL 2.0 C language can be obtained using the following link: https://www.khronos.org/registry/OpenCL/specs/opencl-2.0-openclc.pdf
-
-#### Improved Virtual Addressing (48 bit VA) management for Vega 10 and later GPUs
-* Fixes Clang AddressSanitizer and potentially other 3rd-party memory debugging tools with ROCm
-* Small performance improvement on workloads that do a lot of memory management
-* Removes virtual address space limitations on systems with more VRAM than system memory
-
-#### Kubernetes support
-
-### New features and enhancements in ROCm 1.9.2
-#### RDMA(MPI) support on Vega 7nm
-* Support ROCnRDMA based on Mellanox InfiniBand
-
-#### Improvements to HCC
-* Improved link time optimization
-
-#### Improvements to ROCProfiler tool
-* General bug fixes and implemented versioning APIs
-
-### New features and enhancements in ROCm 1.9.2
-#### RDMA(MPI) support on Vega 7nm
-* Support ROCnRDMA based on Mellanox InfiniBand
-
-#### Improvements to HCC
-* Improved link time optimization
-
-#### Improvements to ROCProfiler tool
-* General bug fixes and implemented versioning APIs
-
-#### Critical bug fixes
-
-### New features and enhancements in ROCm 1.9.1
-#### Added DPM support to Vega 7nm
-* Dynamic Power Management feature is enabled on Vega 7nm.
-
-#### Fix for 'ROCm profiling' that used to fail with a “Version mismatch between HSA runtime and libhsa-runtime-tools64.so.1” error
-
-### New features and enhancements in ROCm 1.9.0
-
-#### Preview for Vega 7nm
-* Enables developer preview support for Vega 7nm
-
-#### System Management Interface
-* Adds support for the ROCm SMI (System Management Interface) library, which provides monitoring and management capabilities for AMD GPUs.
-
-#### Improvements to HIP/HCC
-* Support for gfx906
-* Added deprecation warning for C++AMP.  This will be the last version of HCC supporting C++AMP.
-* Improved optimization for global address space pointers passing into a GPU kernel
-* Fixed several race conditions in the HCC runtime
-* Performance tuning to the unpinned copy engine
-* Several codegen enhancement fixes in the compiler backend
-
-#### Preview for rocprof Profiling Tool
-Developer preview (alpha) of profiling tool rocProfiler. It includes a command-line front-end, `rpl_run.sh`, which enables:
-* Cmd-line tool for dumping public per kernel perf-counters/metrics and kernel timestamps
-* Input file with counters list and kernels selecting parameters
-* Multiple counters groups and app runs supported
-* Output results in CSV format
-
-The tool can be installed from the `rocprofiler-dev` package. It will be installed into: `/opt/rocm/bin/rpl_run.sh`
-
-#### Preview for rocr Debug Agent rocr_debug_agent
-The ROCr Debug Agent is a library that can be loaded by ROCm Platform Runtime to provide the following functionality:
-* Print the state for wavefronts that report memory violation or upon executing a "s_trap 2" instruction.
-* Allows SIGINT (`ctrl c`) or SIGTERM (`kill -15`) to print wavefront state of aborted GPU dispatches.
-* It is enabled on Vega10 GPUs on ROCm1.9.
-
-The ROCm1.9 release will install the ROCr Debug Agent library at `/opt/rocm/lib/librocr_debug_agent64.so`
-
-
-#### New distribution support
-
-* Binary package support for Ubuntu 18.04
-
-#### ROCm 1.9 is ABI compatible with KFD in upstream Linux kernels.
-Upstream Linux kernels support the following GPUs in these releases:
-4.17: Fiji, Polaris 10, Polaris 11
-4.18: Fiji, Polaris 10, Polaris 11, Vega10
-
-Some ROCm features are not available in the upstream KFD:
-* More system memory available to ROCm applications
-* Interoperability between graphics and compute
-* RDMA
-* IPC
-
-To try ROCm with an upstream kernel, install ROCm as normal, but do not install the rock-dkms package. Also add a udev rule to control `/dev/kfd` permissions:
-
-```
-    echo 'SUBSYSTEM=="kfd", KERNEL=="kfd", TAG+="uaccess", GROUP="video"' | sudo tee /etc/udev/rules.d/70-kfd.rules
-```
-
-### New features as of ROCm 1.8.3
-
-* ROCm 1.8.3 is a minor update meant to fix compatibility issues on Ubuntu releases running kernel 4.15.0-33
-
-### New features as of ROCm 1.8
-
-#### DKMS driver installation
-
- * Debian packages are provided for DKMS on Ubuntu
- * RPM packages are provided for CentOS/RHEL 7.4 and 7.5 support
- * See the [ROCT-Thunk-Interface](https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface/tree/roc-1.8.x) and [ROCK-Kernel-Driver](https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/tree/roc-1.8.x) for additional documentation on driver setup
-
-#### New distribution support
-
- * Binary package support for Ubuntu 16.04 and 18.04
- * Binary package support for CentOS 7.4 and 7.5
- * Binary package support for RHEL 7.4 and 7.5
-
-#### Improved OpenMPI via UCX support
-
- * UCX support for OpenMPI
- * ROCm RDMA
-
-### New Features as of ROCm 1.7
-
-#### DKMS driver installation
-
- * New driver installation uses Dynamic Kernel Module Support (DKMS)
- * Only amdkfd and amdgpu kernel modules are installed to support AMD hardware
- * Currently only Debian packages are provided for DKMS (no Fedora suport available)
- * See the [ROCT-Thunk-Interface](https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface/tree/roc-1.7.x) and [ROCK-Kernel-Driver](https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/tree/roc-1.7.x) for additional documentation on driver setup
-
-### New Features as of ROCm 1.5
-
-#### Developer preview of the new OpenCL 1.2 compatible language runtime and compiler
-
- * OpenCL 2.0 compatible kernel language support with OpenCL 1.2 compatible
-   runtime 
- * Supports offline ahead of time compilation today;
-   during the Beta phase we will add in-process/in-memory compilation. 
-
-#### Binary Package support for Ubuntu 16.04
-
-#### Binary Package support for Fedora 24 is not currently available
-
-#### Dropping binary package support for Ubuntu 14.04, Fedora 23
- 
-#### IPC support 
-