Merge from master. Update to 4.5.2 release

Update manifest for ROCm 4.5 release.

README.md

@@ -1,25 +1,133 @@
 
-# AMD ROCm Release Notes v3.8.0
 
-This page describes the features, fixed issues, and information about downloading and installing the ROCm software.
-It also covers known issues in this release.
+# AMD ROCm™ v4.5.2 Release Notes 
 
-- [Supported Operating Systems and Documentation Updates](#Supported-Operating-Systems-and-Documentation-Updates)
-  * [Supported Operating Systems](#Supported-Operating-Systems)
-  * [AMD ROCm Documentation Updates](#AMD-ROCm-Documentation-Updates)
-   
-- [What\'s New in This Release](#Whats-New-in-This-Release)
-  * [Hipfort-Interface for GPU Kernel Libraries](#Hipfort-Interface-for-GPU-Kernel-Libraries)
-  * [ROCm Data Center Tool](#ROCm-Data-Center-Tool)
-  * [Error-Correcting Code Fields in ROCm Data Center Tool](#Error-Correcting-Code-Fields-in-ROCm-Data-Center-Tool)
-  * [Static Linking Libraries](#Static-Linking-Libraries)
-    
-- [Fixed Defects](#Fixed-Defects)
+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.
 
-- [Known Issues](#Known-Issues)
+## INSTALLATION GUIDE UPDATES FOR ROCM V4.5.2 
 
-- [Deploying ROCm](#Deploying-ROCm)
+In this release, users have the option to 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  
+
+For more details, refer to the AMD ROCm Installation Guide v4.5.2 at, 
+
+https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation_new.html
+
+
+## HIP ENHANCEMENTS
+
+
+The ROCm v4.5.2 release consists of the following HIP enhancement. 
+
+### Changes to the roc-obj-ls Tool 
+
+The roc-obj-ls tool is corrected in ROCm v4.5.2, and the command roc-obj-ls <exe> | roc-obj-extract is no longer the preferred syntax.   
+
+Use the roc-obj tool with the following correct command:  
+
+```   
+
+        roc-obj <exe> 
  
+ ```   
+
+For example, 
+
+Extract all ROCm code objects from a list of executables 
+ 
+ ```   
+
+       roc-obj <executable>... 
+ 
+ ```   
+
+Extract all ROCm code objects from a list of executables, and disassemble them 
+ 
+ ```   
+
+       roc-obj --disassemble <executable>... 
+ 
+       # or 
+
+       roc-obj -d <executable>... 
+
+ ```   
+
+Extract all ROCm code objects from a list of executables into dir/ 
+ 
+ ```   
+
+       roc-obj --outdir dir/ <executable>... 
+
+       # or 
+
+       roc-obj -o dir/ <executable>... 
+
+ ```   
+
+Extract only ROCm code objects matching regex over Target ID 
+ 
+ ```   
+
+       roc-obj --target-id gfx9 <executable>... 
+
+        # or 
+
+       roc-obj -t gfx9 <executable>... 
+
+```    
+
+For more information, refer to the HIP Programming Guide at:  
+
+https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_HIP_Programming_Guide.pdf
+
+
+ ## OPENMP DEFECT FIX
+
+Previously, ROCProfiler crashed when the following ROCProfiler options were used in OpenMP programs: 
+
+* --stats  
+
+* --hsa-trace 
+
+This issue is fixed in the OpenMP plugin by ensuring that the contents of a kernel dispatch packet are not accessed after publishing it. The issue is also fixed in ROCTracer by ensuring that the registered exit function is called before the runtime library is closed. 
+ 
+ 
+
+# AMD ROCm™ v4.5 Release Notes 
+
+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.
+
+- Supported Operating Environments and Documentation Updates
+  * [Supported Operating Environments](#Supported-Operating-Environments)
+  * [ROCm Installation Updates](#ROCm-Installation-Updates)
+  * [AMD ROCm Documentation Updates](#AMD-ROCm-Documentation-Updates)
+
+   
+- What\'s New in This Release
+  * [HIP Enhancements](#HIP-Enhancements)
+  * [Unified Memory Support in ROCm](#Unified-Memory-Support-in-ROCm)
+  * [System Management Interface](#System-Management-Interface) 
+  * [ROCm Math and Communication Libraries](#ROCm-Math-and-Communication-Libraries)
+  * [OpenMP Enhancements](#OpenMP-Enhancements)   
+
+- Known Issues in This Release
+  * [Known Issues in This Release](#Known-Issues-in-This-Release)
+
+- Deprecations in This Release
+  * [Deprecations](#Deprecations)
+
 - [Hardware and Software Support](#Hardware-and-Software-Support)
 
 - [Machine Learning and High Performance Computing Software Stack for AMD GPU](#Machine-Learning-and-High-Performance-Computing-Software-Stack-for-AMD-GPU)
@@ -28,201 +136,555 @@ It also covers known issues in this release.
   
 
 
-# Supported Operating Systems 
 
-## Support for Vega 7nm Workstation
+# ROCm Installation Updates
 
-This release extends support to the Vega 7nm Workstation (Vega20 GL-XE) version.
+This document describes the features, fixed issues, and information
+about downloading and installing the AMD ROCm™ software.
 
-## List of Supported Operating Systems
+It also covers known issues and deprecations in this release.
 
-The AMD ROCm platform is designed to support the following operating systems:
+## Supported Operating Environments
 
-* Ubuntu 20.04 (5.4 and 5.6-oem) and 18.04.5 (Kernel 5.4)	
-* CentOS 7.8 & RHEL 7.8 (Kernel 3.10.0-1127) (Using devtoolset-7 runtime support)
-* CentOS 8.2 & RHEL 8.2 (Kernel 4.18.0 ) (devtoolset is not required)
-* SLES 15 SP1
+The AMD ROCm platform supports the following operating systems:
 
-## Fresh Installation of AMD ROCm v3.8 Recommended
-A fresh and clean installation of AMD ROCm v3.8 is recommended. An upgrade from previous releases to AMD ROCm v3.8 is not supported.
-
-For more information, refer to the AMD ROCm Installation Guide at:
-https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html
-
-**Note**: AMD ROCm release v3.3 or prior releases are not fully compatible with AMD ROCm v3.5 and higher versions. You must perform a fresh ROCm installation if you want to upgrade from AMD ROCm v3.3 or older to 3.5 or higher versions and vice-versa.
-
-**Note**: *render group* is required only for Ubuntu v20.04. For all other ROCm supported operating systems, continue to use *video group*.
-
-* For ROCm v3.5 and releases thereafter,the *clinfo* path is changed to -  */opt/rocm/opencl/bin/clinfo*.
-
-* For ROCm v3.3 and older releases, the *clinfo* path remains unchanged -  */opt/rocm/opencl/bin/x86_64/clinfo*.
+| OS                | Kernel              |
+| ---               | ---                 |
+| SLES15 SP3        | 5.3.18-24.49        |
+| RHEL 7.9          | 3.10.0-1160.6.1.el7 |
+| CentOS 7.9        | 3.10.0-1127         |
+| RHEL 8.4          | 4.18.0-193.1.1.el8  |
+| CentOS 8.3        | 4.18.0-193.el8      |
+| Ubuntu 18.04.5    | 5.4.0-71-generic    |
+| Ubuntu 20.04.3HWE | 5.8.0-48-generic    |
 
 
-# AMD ROCm Documentation Updates
+
+## Enhanced Installation Process for ROCm v4.5
+
+In addition to the installation method using the native Package Manager, AMD ROCm v4.5 introduces added methods to install ROCm. With this
+release, the ROCm installation uses the *amdgpu-install* and *amdgpu-uninstall* scripts. 
+
+The *amdgpu-install* script streamlines the installation process by:
+
+-   Abstracting the distribution-specific package installation logic
+
+-   Performing the repository set-up
+
+-   Allowing user to specify the use case and automating the installation of all the required packages,
+
+-   Performing post-install checks to verify whether the installation was performed successfully
+
+-   Installing the uninstallation script
+
+The *amdgpu-uninstall* script allows the removal of the entire ROCm stack by using a single command.
+
+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
+
+**Note:** Graphics use cases are not supported in this release.
+
+For more details, refer to the AMD ROCm Installation Guide v4.5 at,
+
+https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation_new.html
+
+
+# AMD ROCm Documentation Updates 
 
 ## AMD ROCm Installation Guide 
 
-The AMD ROCm Installation Guide in this release includes:
+The AMD ROCm Installation Guide in this release includes the following
+updates:
 
-* Updated Supported Environments
-* HIP Installation Instructions
-* Tensorflow ROCm Port: Basic Installations on RHEL v8.2
+-   New - Installation Guide for ROCm v4.5
 
-https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html
-
-## AMD ROCm - HIP Documentation Updates
-
-* HIP Repository Information
-
-For more information, see 
-
-https://rocmdocs.amd.com/en/latest/Programming_Guides/Programming-Guides.html#hip-repository-information
-
-## ROCm Data Center Tool User Guide
-
-* Error-Correction Codes Field and Output Documentation
-
-For more information, refer to the AMD ROCm Data Center User Guide at
-
-https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_ROCm_DataCenter_Tool_User_Guide.pdf
-
-## General AMD ROCm Documentation Links
-
-Access the following links for more information:
-
-* For AMD ROCm documentation, see 
-
-  https://rocmdocs.amd.com/en/latest/
-
-* For installation instructions on supped 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/Installation-Guide.html#build-amd-rocm
-
-* For AMD ROCm Release History, see
-
-  https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html#amd-rocm-version-history
+    https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation_new.html
 
 
+## AMD Instinct™ High Performance Computing and Tuning
 
-# What\'s New in This Release
+- New - AMD Instinct™ High Performance Computing and Tuning Guide 
 
-## Hipfort-Interface for GPU Kernel Libraries
+   https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD%20Instinct%E2%84%A2High%20Performance%20Computing%20and%20Tuning%20Guide.pdf
+   
+   
+## HIP Documentation
 
-Hipfort is an interface library for accessing GPU Kernels. It provides support to the AMD ROCm architecture from within the Fortran programming language. Currently, the gfortran and HIP-Clang compilers support hipfort. Note, the gfortran compiler belongs to the GNU Compiler Collection (GCC). While hipfc wrapper calls hipcc for the non-fortran kernel source, gfortran is used for FORTRAN applications that call GPU kernels.
+-  HIP installation instructions
 
-The hipfort interface library is meant for Fortran developers with a focus on gfortran users. 
+   https://rocmdocs.amd.com/en/latest/Installation_Guide/HIP-Installation.html
 
-For information on HIPFort installation and examples, see
-https://github.com/ROCmSoftwarePlatform/hipfort
+-   HIP Programming Guide
+
+    https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_HIP_Programming_Guide.pdf
+
+-   HIP API Guide
+
+    https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD-HIP-API-4.5.pdf
+
+-   HIP-Supported CUDA API Reference Guide
+
+    https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_HIP_Supported_CUDA_API_Reference_Guide.pdf
+
+-   AMD ROCm Compiler Reference Guide
+
+    https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_Compiler_Reference_Guide_v4.5.pdf
+
+-   HIP FAQ
+
+    <https://rocmdocs.amd.com/en/latest/Programming_Guides/HIP-FAQ.html#hip-faq>
+   
+
+## System Interface Management
+
+-   System Interface Management (SMI)
+
+    https://rocmdocs.amd.com/en/latest/ROCm_System_Managment/ROCm-System-Managment.html
+    
+
+## AMD ROCm Data Center Tool
+
+- AMD ROCm Data Center Tool API Guide
+
+  https://github.com/RadeonOpenCompute/ROCm/blob/master/RDC_API_Manual_4.5.pdf
+  
+- AMD ROCm Data Center Tool User Guide
+
+  https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_ROCm_DataCenter_Tool_User_Guide_v4.5.pdf
+
+## ROCm SMI API Guide
+
+-   ROCm SMI API Guide
+
+    https://github.com/RadeonOpenCompute/ROCm/blob/master/ROCm_SMI_Manual_4.5.pdf
+
+## ROC Debugger User and API Guide 
+
+-   ROCDebugger User Guide
+
+    https://github.com/RadeonOpenCompute/ROCm/blob/master/ROCDebugger_User_Guide.pdf
+
+-   Debugger API Guide
+
+    https://github.com/RadeonOpenCompute/ROCm/blob/master/ROCDebugger_API_Guide.pdf
+    
+## OpenMP Documentation
+
+- Updated OpenMP documentation 
+
+  https://rocmdocs.amd.com/en/latest/Programming_Guides/openmp_support.html
   
 
-## ROCm Data Center Tool 
+## AMD ROCm General Documentation Links
 
-The ROCm™ Data Center Tool™ simplifies the administration and addresses key infrastructure challenges in AMD GPUs in cluster and datacenter environments. The important features of this tool are:
+-   For AMD ROCm documentation, see
 
-* GPU telemetry  
+    https://rocmdocs.amd.com/en/latest/
 
-* GPU statistics for jobs 
+-   For installation instructions on supported platforms, see
 
-* Integration with third-party tools 
+    https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html
 
-* Open source 
+-   For AMD ROCm binary structure, see
 
-The ROCm Data Center Tool can be used in the standalone mode if all components are installed. The same set of features is also available in a library format that can be used by existing management tools. 
+    https://rocmdocs.amd.com/en/latest/Installation_Guide/Software-Stack-for-AMD-GPU.html
 
-![ScreenShot](https://github.com/Rmalavally/ROCm/blob/master/RDCComponentsrevised.png)
+-   For AMD ROCm release history, see
+
+    https://rocmdocs.amd.com/en/latest/Current_Release_Notes/ROCm-Version-History.html
 
 
-Refer to the ROCm Data Center Tool™ User Guide for more details on the different modes of operation.  
+# What's New in This Release 
 
-NOTE: The ROCm Data Center User Guide is intended to provide an overview of ROCm Data Center Tool features and how system administrators and Data Center (or HPC) users can administer and configure AMD GPUs. The guide also provides an overview of its components and open source developer handbook. 
+## HIP Enhancements
 
-For installation information on different distributions, refer to the ROCm Data Center User Guide at
+The ROCm v4.5 release consists of the following HIP enhancements:
 
-https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_ROCm_DataCenter_Tool_User_Guide.pdf
+### HIP Direct Dispatch
+
+The conventional producer-consumer model where the host thread(producer) enqueues commands to a command queue (per stream), which is then
+processed by a separate, per-stream worker thread (consumer) created by the runtime, is no longer applicable.
+
+In this release, for Direct Dispatch, the runtime directly queues a packet to the AQL queue (user mode queue to GPU) in Dispatch and some of
+the synchronization. This new functionality indicates the total latency of the HIP Dispatch API and the latency to launch the first wave on the
+GPU.
+
+In addition, eliminating the threads in runtime has reduced the variance in the dispatch numbers as the thread scheduling delays and
+atomics/locks synchronization latencies are reduced.
+
+This feature can be disabled by setting the following environment variable,
+
+```     
+     AMD_DIRECT_DISPATCH=0
+
+```
+
+### Support for HIP Graph 
+
+ROCm v4.5 extends support for HIP Graph. For details, refer to the HIP API Guide at
+
+https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD-HIP-API-4.5.pdf
+
+### Enhanced *launch_bounds* Check Error Log Message 
+
+When a kernel is launched with HIP APIs, for example, hipModuleLaunchKernel(), HIP validates to check that input kernel
+dimension size is not larger than specified launch_bounds.
+
+If exceeded, HIP returns launch failure if AMD_LOG_LEVEL is set with the proper value. Users can find more information in the error log message,
+including launch parameters of kernel dim size, launch bounds, and the name of the faulting kernel. It is helpful to figure out the faulting
+kernel. Besides, the kernel dim size and launch bounds values will also assist in debugging such failures.
+
+For more details, refer to the HIP Programming Guide at
+
+https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_HIP_Programming_Guide.pdf
 
 
-### Error Correcting Code Fields in ROCm Data Center Tool
+### HIP Runtime Compilation
 
-The ROCm Data Center (RDC) tool is enhanced to provide counters to track correctable and uncorrectable errors. While a single bit per word error can be corrected, double bit per word errors cannot be corrected. 
+HIP now supports runtime compilation (hipRTC), the usage of which will provide the possibility of optimizations and performance improvement
+compared with other APIs via regular offline static compilation. 
 
-The RDC tool now helps monitor and protect undetected memory data corruption. If the system is using ECC- enabled memory, the ROCm Data Center tool can report the error counters to monitor the status of the memory. 
+hipRTC APIs accept HIP source files in character string format as input parameters and create handles of programs by compiling the HIP source
+files without spawning separate processes.
 
-![ScreenShot](https://github.com/Rmalavally/ROCm/blob/master/forweb.PNG)
+For more details on hipRTC APIs, refer to the HIP API Guide at
 
-## Static Linking Libraries 
+https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD-HIP-API-4.5.pdf
 
-The underlying libraries of AMD ROCm are dynamic and are called shared objects (.so) in Linux.
-The AMD ROCm v3.8 release includes the capability to build static ROCm libraries and link to the applications statically. CMake target files enable linking an application statically to ROCm libraries and each component exports the required dependencies for linking. The static libraries are called Archives (.a) in Linux.
+### New Flag for Backwards Compatibility on float/double atomicAdd Function
 
-This release also comprises of the requisite changes required for all the components to work in a static environment. The components have been successfully tested for basic functionalities like *rocminfo /rocm_bandwidth_test* and archives.
+In the ROCm4.5 release, a new compilation flag is introduced as an option in the CMAKE file. This flag ensures backwards compatibility in
+float/double atomicAdd functions.
 
-In the AMD ROCm v3.8 release, the following libraries support static linking: 
+```   
+     \_\_HIP_USE_CMPXCHG_FOR_FP_ATOMICS
+```   
 
-![ScreenShot](https://github.com/Rmalavally/ROCm/blob/master/staticlinkinglib.PNG)
+This compilation flag is not set("0") by default, so the HIP runtime uses the current float/double atomicAdd functions.
 
-# Fixed Defects
-The following defects are fixed in this release:
+If this compilation flag is set to "1" with the CMAKE option, the existing float/double atomicAdd functions is used for compatibility with
+compilers that do not support floating point atomics.
 
-* GPU Kernel C++ Names Not Demangled
-* MIGraphX Fails for fp16 Datatype
-* Issue with Peer-to-Peer Transfers
-* ‘rocprof’ option ‘--parallel-kernels’ Not Supported in this Release
+```  
+     D\_\_HIP_USE_CMPXCHG_FOR_FP_ATOMICS=1
+```  
+For details on how to build the HIP runtime, refer to the HIP Programming Guide at
 
-# Known Issues 
+https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_HIP_Programming_Guide.pdf
 
-## Undefined Reference Issue in Statically Linked Libraries
 
-Libraries and applications statically linked using flags -rtlib=compiler-rt, such as rocBLAS, have an implicit dependency on gcc_s not captured in their CMAKE configuration.  
 
-Client applications may require linking with an additional library -lgcc_s to resolve the undefined reference to symbol '_Unwind_Resume@@GCC_3.0'.
+### Updated HIP Version Definition
 
-## MIGraphX Pooling Operation Fails for Some Models
+The HIP version definition is updated as follows:
 
-MIGraphX does not work for some models with pooling operations and the following error appears:
+```  
+     HIP_VERSION=HIP_VERSION_MAJOR * 10000000 + HIP_VERSION_MINOR *
+     100000 + HIP_VERSION_PATCH)
+```  
 
-*‘test_gpu_ops_test FAILED’*
+The HIP version can be queried from the following HIP API call,
 
-This issue is currently under investigation and there is no known workaround currently. 
+```  
+     hipRuntimeGetVersion(&runtimeVersion);
+```  
 
-## MIVisionX Installation Error on CentOS/RHEL8.2 and SLES 15
+The version returned is always greater than the versions in the previous ROCm releases.
 
-Installing ROCm on MIVisionX results in the following error on CentOS/RHEL8.2 and SLES 15:
+**Note:** The version definition of the HIP runtime is different from that of CUDA. The function returns the HIP runtime version on the AMD
+platform, while on the NVIDIA platform, it returns the CUDA runtime version. There is no mapping or a correlation between the HIP and CUDA
+versions.
 
-*"Problem: nothing provides opencv needed"*
 
-As a workaround, install opencv before installing MIVisionX.
+
+### Planned HIP Enhancements and Fixes
+
+#### Changes to hiprtc implementation to match nvrtc behavior
+
+In this release, there are changes to the *hiprtc* implementation to
+match the *nvrtc* behavior.
+
+**Impact:** Applications can no longer explicitly include HIP runtime header files. Minor code changes are required to remove the HIP runtime
+header files.
+
+#### HIP device attribute enumeration
+
+In a future release, there will be a breaking change in the HIP device attribute enumeration. Enum values are being rearranged to accommodate
+future enhancements and additions.
+
+**Impact:** This will require users to rebuild their applications. No code changes are required.
+
+#### Changes to behavior of hipGetLastError() and hipPeekAtLastError() to match CUDA behavior available
+
+In a later release, changes to behavior of hipGetLastError() and hipPeekAtLastError() to match CUDA behavior will be available.
+
+**Impact:** Applications relying on the previous behavior will be impacted and may require some code changes.
+
+## Unified Memory Support in ROCm
+
+Unified memory allows applications to map and migrate data between CPU and GPU seamlessly without explicitly copying it between different
+allocations. This enables a more complete implementation of *hipMallocManaged*, *hipMemAdvise*, *hipMemPrefetchAsync* and related
+APIs. Without unified memory, these APIs only support system memory. With unified memory, the driver can automatically migrate such memory to
+GPU memory for faster access.
+
+### Supported Operating Systems and Versions
+
+This feature is only supported on recent Linux kernels. Currently, it works on Ubuntu versions with 5.6 or newer kernels and the DKMS driver
+from ROCm. Current releases of RHEL and SLES do not support this feature yet. Future releases of those distributions will add support for this.
+The unified memory feature is also supported in the KFD driver included with upstream kernels starting from Linux 5.14.
+
+Unified memory only works on GFXv9 and later GPUs, including Vega10 and MI100. Fiji, Polaris and older GPUs are not supported. To check whether
+unified memory is enabled, look in the kernel log for this message:
+
+```  
+     \$ dmesg \| grep \"HMM registered"
+```  
+
+If unified memory is enabled, there should be a message like "HMM registered xyzMB device memory". If unified memory is not supported on
+your GPU or kernel version, this message is missing.
+
+### Unified Memory Support and XNACK
+
+Unified memory support comes in two flavours, XNACK-enabled and XNACK-disabled. XNACK refers to the ability of the GPU to handle page
+faults gracefully and retry a memory access. In XNACK-enabled mode, the GPU can handle retry after page-faults, which enables mapping and
+migrating data on demand, as well as memory overcommitment. In XNACK-disabled mode, all memory must be resident and mapped in the GPU
+page tables when the GPU is executing application code. Any migrations involve temporary preemption of the GPU queues by the driver. Both page
+fault handling and preemptions, happen automatically and are transparent to the applications.
+
+XNACK-enabled mode only has experimental support. XNACK-enabled mode requires compiling shader code differently. By default, the ROCm
+compiler builds code that works in both modes. Code can be optimized for one specific mode with compiler options:
+
+OpenCL:
+
+```  
+     clang \... -mcpu=gfx908:xnack+:sramecc- \... // xnack on, sramecc off\
+     clang \... -mcpu=gfx908:xnack-:sramecc+ \... // xnack off, sramecc on
+```  
+
+HIP:
+```  
+     clang \... \--cuda-gpu-arch=gfx906:xnack+ \... // xnack on\
+     clang \... \--cuda-gpu-arch=gfx906:xnack- \... // xnack off
+```  
+Not all the math libraries included in ROCm support XNACK-enabled mode on current hardware. Applications will fail to run if their shaders are
+compiled in the incorrect mode.
+
+On current hardware, the XNACK mode can be chosen at boot-time by a module parameter amdgpu.noretry. The default is XNACK-disabled
+(amdgpu.noretry=1).
+
+## System Management Interface 
+
+### Enhanced ROCm SMI --setpoweroverdrive Functionality
+
+The ROCm System Management Interface (SMI) *--setpoweroverdrive* functionality is used to lower the power cap on a device without needing
+to enable the OverDrive functionality in the driver. Similarly, even with the OverDrive driver functionality enabled, it is possible to
+request a lower power cap than the card's default.
+
+Currently, any use of the *--setpoweroverdrive* functionality in rocm-smi prints an out-of-spec warning to the screen and requires the
+user to agree that using this functionality potentially voids their warranty. However, this warning should only be printed when users are
+trying to set the power cap to higher than the card's default, which requires the OverDrive driver functionality to be enabled.
+
+For example:
+
+The default power cap is 225.0W before any changes.
+
+```
+
+     \[atitest\@rhel85 smi\]\$ ./rocm_smi.py --resetpoweroverdrive
+     ======================= ROCm System Management Interface =======================
+
+     ========================== Reset GPU Power OverDrive ===========================
+
+     GPU\[0\] : Successfully reset Power OverDrive to: 225W
+     ============================ End of ROCm SMI Log ============================
+
+     Now, after using --setpoweroverdrive to lower the power cap to 123
+     watts:
+
+     \[atitest\@rhel85 smi\]\$ ./rocm_smi.py --setpoweroverdrive 123
+     ======================= ROCm System Management Interface =======================
+
+     =========================== Set GPU Power OverDrive ============================
+
+     GPU\[0\] : Successfully set power to: 123W
+     ======================= End of ROCm SMI Log ==============================
+
+     Setting a power cap lower than the default of 225.0W (in this case,
+     123W) does not give a warning.
+
+     To verify that the power is set to the correct value:
+
+     \[atitest\@rhel85 smi\]\$ ./rocm_smi.py --showmaxpower
+     ======================= ROCm System Management Interface =======================
+
+     ======================== Power Cap ===================================
+
+     GPU\[0\] : Max Graphics Package Power (W): 123.0
+     ========================End of ROCm SMI Log ==============================
+```
+
+
+## OpenMP Enhancements
+
+The ROCm installation includes an LLVM-based implementation, which fully supports OpenMP 4.5 standard and a subset of the OpenMP 5.0 standard.
+Fortran and C/C++ compilers and corresponding runtime libraries are included. Along with host APIs, the OpenMP compilers support offloading
+code and data onto GPU devices.
+
+For more information, refer to
+
+<https://rocmdocs.amd.com/en/latest/Programming_Guides/openmp_support.html>
+
+## ROCm Math and Communication Libraries
+
+In this release, ROCm Math and Communication Libraries consists of the
+following enhancements and fixes:
+
+| Library   | Changes                                                  |
+| ---       | ---                                                      |
+| rocBLAS | **Optimizations** <ul><li>Improved performance of non-batched and batched syr for all sizes and data types</li><li>Improved performance of non-batched and batched hemv for all sizes and data types</li><li>Improved performance of non-batched and batched symv for all sizes and data types</li><li>Improved memory utilization in rocblas-bench, rocblas-test gemm functions, increasing possible runtime sizes.</li></ul>**Changes** <ul><li>Update from C++14 to C++17.</li>  <li>Packaging split into a runtime package (called rocblas) and a development package (called rocblas-dev for .deb packages, and rocblas-devel for .rpm packages). The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The 'suggest' feature in packaging is introduced as a deprecated feature and will be removed in a future ROCm release.</li></ul> **Fixed**<ul><li>For function geam avoid overflow in offset calculation.</li>  <li> For function syr avoid overflow in offset calculation.</li> <li>For function gemv (Transpose-case) avoid overflow in offset calculation.</li> <li>For functions ssyrk and dsyrk, allow conjugate-transpose case to match legacy BLAS. Behavior is the same as the transpose case.</li></ul> |
+| hipBLAS| **Added**<ul><li>More support for hipblas-bench</li></ul>**Fixed**<ul><li>Avoid large offset overflow for gemv and hemv in hipblas-test</li></ul>**Changed**<ul><li>Packaging split into a runtime package called hipblas and a development package called hipblas-devel. The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The 'suggests' feature in packaging is a transitional feature and will be removed in a future rocm release.</li></ul> |
+| rocFFT | **Optimizations**<ul><li>Optimized SBCC kernels of length 52, 60, 72, 80, 84, 96, 104, 108, 112, 160, 168, 208, 216, 224, 240 with new kernel generator.</li></ul>**Added**<ul><li>Split 2D device code into separate libraries.</li> </ul>**Changed**<ul><li>Packaging split into a runtime package called rocfft and a development package called rocfft-devel. The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The suggests feature in packaging is introduced as a deprecated feature and will be removed in a future rocm release.</li></ul>**Fixed**<ul><li>Fixed a few validation failures of even-length R2C inplace. 2D, 3D cubics sizes such as 100^2 (or ^3), 200^2 (or ^3), 256^2 (or ^3)...etc. We don't combine the three kernels (stockham-r2c-transpose). We only combine two kernels (r2c-transpose) instead.</li></ul> |
+| hipFFT | **Changed**  <ul><li>Packaging split into a runtime package called hipfft and a development package called hipfft-devel. The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The 'suggests' feature in packaging is a transitional feature and will be removed in a future rocm release.</li></ul> |
+| rocSPARSE | **Added** <ul><li>Triangular solve for multiple right-hand sides using BSR format</li> <li>SpMV for BSRX format</li> <li>SpMM in CSR format enhanced to work with transposed A</li> <li>Matrix coloring for CSR matrices </li><li>Added batched tridiagonal solve (gtsv_strided_batch)</li></ul> **Improved** <ul><li>Fixed a bug with gemvi on Navi21 </li><li>Optimization for pivot based gtsv</li></ul> |
+| hipSPARSE | **Added** <ul><li>Triangular solve for multiple right-hand sides using BSR format</li> <li>SpMV for BSRX format</li> <li>SpMM in CSR format enhanced to work with transposed A</li> <li>Matrix coloring for CSR matrices </li>  <li>Added batched tridiagonal solve (gtsv_strided_batch)</li></ul> **Improved** <ul><li>Fixed a bug with gemvi on Navi21</li> <li>Optimization for pivot based gtsv</li></ul> |
+| rocALUTION | **Changed** <ul><li>Packaging split into a runtime package called rocalution and a development package called rocalution-devel. The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The 'suggests' feature in packaging is a transitional feature and will be removed in a future rocm release.</li></ul> **Improved** <ul><li>(A)MG solving phase optimization</li></ul> |
+| rocTHRUST | **Changed**  <ul><li>Packaging changed to a development package (called rocthrust-dev for .deb packages, and rocthrust-devel for .rpm packages). As rocThrust is a header-only library, there is no runtime package. To aid in the transition, the development package sets the "provides" field to provide the package rocthrust, so that existing packages depending on rocthrust can continue to work. The 'provides' feature is a transitional feature and will be removed in a future ROCm release.</li></ul> |
+| rocSOLVER | **Added** <ul><li>RQ factorization routines:</li><li>GERQ2, GERQF (with batched and strided_batchedversions)</li>  <li>Linear solvers for general square systems:</li> <li>GESV (with batched and strided_batched versions)</li><li>Linear solvers for symmetric/hermitian positive definite systems:</li> <li>POTRS (with batched and strided_batched versions)</li> <li>POSV (with batched and strided_batched versions) </li> <li>Inverse of symmetric/hermitian positive definite matrices:</li><li>POTRI (with batched and strided_batched versions)</li> <li>General matrix inversion without pivoting:  </li>  <li>GETRI_NPVT (with batched and strided_batched versions)</li> <li>GETRI_NPVT_OUTOFPLACE (with batched and  strided_batched versions)</li></ul>**Optimized**<ul><li>Improved performance of LU factorization (especially for large matrix sizes)</li> <li>Changed</li>  <li>Raised reference LAPACK version used for rocSOLVER test and benchmark clients to v3.9.1</li>  <li>Minor CMake improvements for users building from source without install.sh:</li> <li>Removed fmt::fmt from rocsolver\'s public usage requirements</li> <li>Enabled small-size optimizations by default </li>  <li>Split packaging into a runtime package ('rocsolver') and a development package ('rocsolver-devel'). The development package depends on the runtime package. To aid in the transition, the runtime package suggests the development package (except on CentOS 7). This use of the 'suggests feature' is transitional and will be removed in a future ROCm release.</li></ul> **Fixed** <ul><li>Use of the GCC / Clang __attribute__((deprecated(...))) extension is now guarded by compiler detection macros. |
+| hipSOLVER | The following functions were added in this release:<ul><li>gesv</li><ul><li>hipsolverSSgesv_bufferSize, hipsolverDDgesv_bufferSize, hipsolverCCgesv_bufferSize, hipsolverZZgesv_bufferSize</li><li>hipsolverSSgesv, hipsolverDDgesv, hipsolverCCgesv, hipsolverZZgesv</li></ul><li>potrs</li><ul><li>hipsolverSpotrs_bufferSize, hipsolverDpotrs_bufferSize, hipsolverCpotrs_bufferSize, hipsolverZpotrs_bufferSize</li><li>hipsolverSpotrs, hipsolverDpotrs, hipsolverCpotrs, hipsolverZpotrs</li></ul><li>potrsBatched</li><ul><li>hipsolverSpotrsBatched_bufferSize, hipsolverDpotrsBatched_bufferSize, hipsolverCpotrsBatched_bufferSize, hipsolverZpotrsBatched_bufferSize</li><li>hipsolverSpotrsBatched, hipsolverDpotrsBatched, hipsolverCpotrsBatched, hipsolverZpotrsBatched</li></ul><li>potri</li><ul><li>hipsolverSpotri_bufferSize, hipsolverDpotri_bufferSize, hipsolverCpotri_bufferSize, hipsolverZpotri_bufferSize</li><li>hipsolverSpotri, hipsolverDpotri, hipsolverCpotri, hipsolverZpotri</li></ul></ul></li></ul> |
+| RCCL | **Added** <ul><li>Compatibility with NCCL 2.9.9 </li></ul>**Changed**  <ul><li>Packaging split into a runtime package called rccl and a development package called rccl-devel. The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The 'suggests' feature in packaging is a tranistional feature and will be removed in a future rocm release.</li></ul> |
+| hipCUB | **Changed**  <ul><li>Packaging changed to a development package (called hipcub-dev for .deb packages, and hipcub-devel for .rpm packages). As hipCUB is a header-only library, there is no runtime package. To aid in the transition, the development package sets the "provides" field to provide the package hipcub, so that existing packages depending on hipcub can continue to work. This provides feature is introduced as a deprecated feature and will be removed in a future ROCm release.</li></ul> |
+| rocPRIM| **Added** <ul><li>bfloat16 support added.</li></ul> **Changed**  <ul><li>Packaging split into a runtime package called rocprim and a development package called rocprim-devel. The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The suggests feature in packaging is introduced as a deprecated feature and will be removed in a future rocm release.</li> <li>As rocPRIM is a header-only library, the runtime package is an empty placeholder used to aid in the transition. This package is also a deprecated feature and will be removed in a future rocm release.</li></ul> **Deprecated** <ul><li>The warp_size() function is now deprecated; please switch to host_warp_size() and device_warp_size() for host and device references respectively.</li></ul> |
+| rocRAND| **Changed**  <ul><li>Packaging split into a runtime package called rocrand and a development package called rocrand-devel. The development package depends on runtime. The runtime package suggests the development package for all supported OSes except CentOS 7 to aid in the transition. The suggests feature in packaging is introduced as a deprecated feature and will be removed in a future rocm release.</li></ul> **Fixed** <ul><li>Fix for mrg_uniform_distribution_double generating incorrect range of values</li> <li>Fix for order of state calls for log_normal, normal, and uniform</li></ul> **Known issues**  <ul><li>kernel_xorwow test is failing for certain GPU architectures.</li></ul> |
+
+For more information about ROCm Libraries, refer to the documentation at
+
+<https://rocmdocs.amd.com/en/latest/ROCm_Libraries/ROCm_Libraries.html>
+
+# Known Issues in This Release 
+
+The following are the known issues in this release.
+
+## clinfo and rocminfo Do Not Display Marketing Name
+
+clinfo and rocminfo display a blank field for Marketing Name. 
+
+This is due to a missing package that is not yet available from ROCm. This package will be distributed in future ROCm releases.
+
+## Compiler Support for Function Pointers and Virtual Functions
+
+A known issue in the compiler support for function pointers and virtual functions on the GPU may cause undefined behavior due to register
+corruption. 
+
+A temporary workaround is to compile the affected application with this option:
+
+```
+     -mllvm -amdgpu-fixed-function-abi=1
+     
+ ```
+
+**Note:** This is an internal compiler flag and may be removed without notice once the issue is addressed in a future release.
+
+
+## Debugger Process Exit May Cause ROCgdb Internal Error
+
+If the debugger process exits during debugging, ROCgdb may report internal errors. This issue occurs as it attempts to access the AMD GPU
+state for the exited process. To recover, users must restart ROCgdb.
+ 
+As a workaround, users can set breakpoints to prevent the debugged process from exiting. For example, users can set breakpoints at the last
+statement of the main function and in the abort() and exit() functions. This temporary solution allows the application to be re-run without
+restarting ROCgdb.
+
+This issue is currently under investigation and will be fixed in a future release.
+
+For more information, refer to the ROCgdb User Guide at,
+
+https://github.com/RadeonOpenCompute/ROCm/blob/master/ROCDebugger_User_Guide.pdf
+
+## Cache Issues with ROCProfiler
+
+When the same kernel is launched back-to-back multiple times on a GPU, a cache flush is executed each time the kernel finishes when profiler data is collected. The cache flush is inserted by ROCprofiler for each kernel. This prevents kernel from being cached, instead it is being read each time it is launched. As a result the cache hit rate from rocprofiler is reported as 0% or very low.
+
+This issue is under investigation and will be fixed in a future release. 
+
+## Stability Issue on LAMMPS-KOKKOS Applications
+
+On mGPU machines, lammps-kokkos applications experience a stability issue (AMD Instinct MI100™). 
+
+As a workaround, perform a Translation LookAside Buffer (TLB) flush. 
+
+The issue is under active investigation and will be resolved in a future release.
+
+
+
+# Deprecations
+
+## AMD Instinct MI25 End of Life
+
+ROCm release v4.5 is the final release to support AMD Instinct MI25. AMD Instinct MI25 has reached End of Life (EOL). ROCm 4.5 represents the
+last certified release for software and driver support. AMD will continue to provide technical support and issue resolution for AMD
+Instinct MI25 on ROCm v4.5 for a period of 12 months from the software GA date. 
+
+## Planned Deprecation for Code Object Versions 2 and 3 
+
+With the ROCm v4.5 release, the generation of code object versions 2 and 3 is being deprecated and may be removed in a future release. This deprecation notice does not impact support for the execution of AMD GPU code object versions.
+
+The -mcode-object-version Clang option can be used to instruct the compiler to generate a specific AMD GPU code object version. In ROCm v4.5, the compiler can generate AMD GPU code object version 2, 3, and 4, with version 4 being the default if not specified. 
+
 
 
 # Deploying ROCm
-AMD hosts both Debian and RPM repositories for the ROCm v3.8.x packages. 
+
+AMD hosts both Debian and RPM repositories for the ROCm packages. 
 
 For more information on ROCM installation on all platforms, see
 
 https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html
 
+
+# Machine Learning and High Performance Computing Software Stack for AMD GPU
+
+For an updated version of the software stack for AMD GPU, see
+
+https://rocmdocs.amd.com/en/latest/Installation_Guide/Software-Stack-for-AMD-GPU.html
+
+
+
 # Hardware and Software 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.
 
+**Note:** The AMD ROCm™ open software platform is a compute stack for headless system deployments. GUI-based software applications are currently not supported.
+
 #### 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.
 
+**Note:** The integrated GPUs of Ryzen are not officially supported targets for ROCm.
+
 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
-  * 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
+* 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, Radeon Pro VII
+
+* CDNA GPUs
+
+  - MI100 chips such as on the AMD Instinct™ MI100
+
 
 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:
 
   * GFX8 GPUs
@@ -238,7 +700,7 @@ As described [below](#limited-support), "Carrizo", "Bristol Ridge", and "Raven R
 However, they are not enabled in the HIP runtime, 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).
+For a more detailed list of hardware support, please see [the following documentation](https://en.wikipedia.org/wiki/List_of_AMD_graphics_processing_units).
 
 #### Supported CPUs
 As described above, GFX8 GPUs require PCIe 3.0 with PCIe atomics in order to run ROCm.
@@ -281,7 +743,7 @@ from the list provided above for compatibility purposes.
 
 ##### Limited support
 
-* ROCm 2.9.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_.
+* ROCm 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.1.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 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.
@@ -294,11 +756,13 @@ from the list provided above for compatibility purposes.
 
 ##### Not supported
 
-* "Tonga", "Iceland", "Vega M", and "Vega 12" GPUs are not supported in ROCm 2.9.x
+* "Tonga", "Iceland", "Vega M", and "Vega 12" GPUs are not supported.
 * 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.
 
+In the default ROCm configuration, GFX8 and GFX9 GPUs require PCI Express 3.0 with PCIe atomics. The ROCm platform leverages these advanced capabilities to allow features such as user-level submission of work from the host to the GPU. This includes PCIe atomic Fetch and Add, Compare and Swap, Unconditional Swap, and AtomicOp Completion.
+
 #### 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.
@@ -325,9 +789,16 @@ For users that have the option of using either AMD's or the upstreamed driver, t
 |      |   | Does not include most up-to-date firmware |
 
 
+# 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. 
+
+
+
 
-## Machine Learning and High Performance Computing Software Stack for AMD GPU
 
-For an updated version of the software stack for AMD GPU, see
 
-https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html#software-stack-for-amd-gpu

default.xml

@@ -1,27 +1,26 @@
 <?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/" />
+fetch="https://github.com/GPUOpen-Tools/" />
     <remote name="KhronosGroup"
-            fetch="https://github.com/KhronosGroup/" />
-    <default revision="refs/tags/rocm-3.8.0"
-             remote="roc-github"
-             sync-c="true"
-             sync-j="4" />
-    <!--list of projects for ROCM-->
+fetch="https://github.com/KhronosGroup/" />
+    <default revision="refs/tags/rocm-4.5.2"
+     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_smi_lib" remote="roc-github" />
+    <project name="rocm_smi_lib" />
     <project name="rocm-cmake" />
     <project name="rocminfo" />
     <project name="rocprofiler" remote="rocm-devtools" />
@@ -29,51 +28,50 @@
     <project name="ROCm-OpenCL-Runtime" />
     <project path="ROCm-OpenCL-Runtime/api/opencl/khronos/icd" name="OpenCL-ICD-Loader" remote="KhronosGroup" revision="6c03f8b58fafd9dd693eaac826749a5cfad515f8" />
     <project name="clang-ocl" />
-    <!--HIP Projects-->
+<!--HIP Projects-->
     <project name="HIP" remote="rocm-devtools" />
+    <project name="hipamd" remote="rocm-devtools" />
     <project name="HIP-Examples" remote="rocm-devtools" />
     <project name="ROCclr" remote="rocm-devtools" />
     <project name="HIPIFY" remote="rocm-devtools" />
-    <!-- The following projects are all associated with the AMDGPU LLVM compiler -->
-    <project name="llvm-project" path="llvm_amd-stg-open" />
+<!-- The following projects are all associated with the AMDGPU LLVM compiler -->
+    <project name="llvm-project" />
     <project name="ROCm-Device-Libs" />
     <project name="atmi" />
     <project name="ROCm-CompilerSupport" />
     <project name="rocr_debug_agent" remote="rocm-devtools" />
     <project name="rocm_bandwidth_test" />
+    <project name="half" remote="rocm-swplat" revision="37742ce15b76b44e4b271c1e66d13d2fa7bd003e" />
     <project name="RCP" remote="gpuopen-tools" revision="3a49405a1500067c49d181844ec90aea606055bb" />
-    <!-- gdb projects -->
+<!-- gdb projects -->
     <project name="ROCgdb" remote="rocm-devtools" />
     <project name="ROCdbgapi" remote="rocm-devtools" />
-    <!-- ROCm Libraries -->
+<!-- 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="MIOpenTensile" 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="hipfort" remote="rocm-swplat" />
+    <project name="AMDMIGraphX" remote="rocm-swplat" />
     <project name="ROCmValidationSuite" remote="rocm-devtools" />
-    <!-- Projects for AOMP -->
-    <project name="ROCT-Thunk-Interface" path="aomp/roct-thunk-interface" remote="roc-github" />
-    <project name="ROCR-Runtime" path="aomp/rocr-runtime" remote="roc-github" />
-    <project name="ROCm-Device-Libs" path="aomp/rocm-device-libs" remote="roc-github" />
-    <project name="ROCm-CompilerSupport" path="aomp/rocm-compilersupport" remote="roc-github" />
-    <project name="rocminfo" path="aomp/rocminfo" remote="roc-github" />
-    <project name="HIP" path="aomp/hip-on-vdi" remote="rocm-devtools" />
-    <project name="aomp" path="aomp/aomp" remote="rocm-devtools" />
-    <project name="aomp-extras" path="aomp/aomp-extras" remote="rocm-devtools" />
-    <project name="flang" path="aomp/flang" remote="rocm-devtools" />
-    <project name="amd-llvm-project" path="aomp/amd-llvm-project" remote="rocm-devtools" />
-    <project name="ROCclr" path="aomp/vdi" remote="rocm-devtools" />
-    <project name="ROCm-OpenCL-Runtime" path="aomp/opencl-on-vdi" remote="roc-github" />
+<!-- 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>

images/test.rst

@@ -0,0 +1 @@
+