4.2 : Manifest Files

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

README.md

@@ -1,23 +1,27 @@
+# AMD ROCm™ v4.2 Release Notes 
 
-# 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.
+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 Systems and Documentation Updates](#Supported-Operating-Systems-and-Documentation-Updates)
   * [Supported Operating Systems](#Supported-Operating-Systems)
+  * [ROCm Installation Updates](#ROCm-Installation-Updates)
   * [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)
+  * [HIP Enhancements](#HIP-Enhancements)
   * [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)
+  * [ROCm Math and Communication Libraries](#ROCm-Math-and-Communication-Libraries)   
+
+
+- [Fixed Defects](#Fixed-Defects)  
 
 - [Known Issues](#Known-Issues)
 
+- [Deprecations](#Deprecations)
+
+  * [Compiler Generated Code Object Version 2 Deprecation ](#Compiler-Generated-Code-Object-Version-2-Deprecation)
+
 - [Deploying ROCm](#Deploying-ROCm)
  
 - [Hardware and Software Support](#Hardware-and-Software-Support)
@@ -28,34 +32,74 @@ 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.
-
-## List of Supported Operating Systems
+### Supported Operating Systems
 
 The AMD ROCm platform is designed to support the following operating systems:
 
-* 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
+* Ubuntu 20.04.2 HWE (5.4 and 5.6-oem) and 18.04.5 (Kernel 5.4) 
+* CentOS 7.9 (3.10.0-1127) & RHEL 7.9 (3.10.0-1160.6.1.el7) (Using devtoolset-7 runtime support) 
+* CentOS 8.3 (4.18.0-193.el8)and RHEL 8.3 (4.18.0-193.1.1.el8) (devtoolset is not required) 
+* SLES 15 SP2
 
-## 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:
+
+### Complete Installation of AMD ROCM V4.2 Recommended
+
+Complete uninstallation of previous ROCm versions is required before installing a new version of ROCm. **An upgrade from previous releases to AMD ROCm v4.2 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*.
+**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.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*.
+* For ROCm v3.3 and older releases, the clinfo path remains /opt/rocm/opencl/bin/x86_64/clinfo. 
+ 
+## ROCm Multi-Version Installation Update
+
+With the AMD ROCm v4.2 release, the following ROCm multi-version installation changes apply:
+
+The meta packages rocm-dkms<version> are now deprecated for multi-version ROCm installs.  For example, rocm-dkms3.7.0, rocm-dkms3.8.0.
+ 
+* Multi-version installation of ROCm should be performed by installing rocm-dev<version> using each of the desired ROCm versions. For example, rocm-dev3.7.0, rocm-dev3.8.0, rocm-dev3.9.0.   
+
+* The rock-dkms loadable kernel modules should be installed using a single rock-dkms package. 
+
+* ROCm v3.9 and above will not set any ldconfig entries for ROCm libraries for multi-version installation.  Users must set LD_LIBRARY_PATH to load the ROCm library version of choice.
+
+**NOTE**: The single version installation of the ROCm stack remains the same. The rocm-dkms package can be used for single version installs and is not deprecated at this time.
+
+
+### Updated HIP Instructions for ROCm Installation
+
+The hip-base package has a dependency on Perl modules that some operating systems may not have in their default package repositories.  Use the following commands to add repositories that have the required Perl packages:
+
+
+#### For SLES 15 SP2
+
+		sudo zypper addrepo 
+
+
+For more information, see
+
+https://download.opensuse.org/repositories/devel:languages:perl/SLE_15/devel:languages:perl.repo
+
+
+
+#### For CentOS8.3
+
+		sudo yum config-manager --set-enabled powertools
+	
+
+#### For RHEL8.3
+
+		sudo subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms
+ 
 
 
 # AMD ROCm Documentation Updates
@@ -64,27 +108,76 @@ https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html
 
 The AMD ROCm Installation Guide in this release includes:
 
-* Updated Supported Environments
-* HIP Installation Instructions
-* Tensorflow ROCm Port: Basic Installations on RHEL v8.2
+* Supported Environments
+
+* Installation Instructions 
+
+* HIP Installation Instructions 
+
+For more information, refer to the ROCm documentation website at:
+
+https://rocmdocs.amd.com/en/latest/
 
-https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html
 
 ## AMD ROCm - HIP Documentation Updates
 
-* HIP Repository Information
+* HIP Programming Guide v4.2 
 
-For more information, see 
+https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD%20HIP%20Programming%20Guide_v4.2.pdf
+ 
 
-https://rocmdocs.amd.com/en/latest/Programming_Guides/Programming-Guides.html#hip-repository-information
+* HIP API Guide v4.2
 
-## ROCm Data Center Tool User Guide
+https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_HIP_API_Guide_4.2.pdf
+  
 
-* Error-Correction Codes Field and Output Documentation
+* HIP-Supported CUDA API Reference Guide v4.2
 
-For more information, refer to the AMD ROCm Data Center User Guide at
+https://github.com/RadeonOpenCompute/ROCm/blob/master/HIP_Supported_CUDA_API_Reference_Guide_v4.2.pdf  
+
+* HIP FAQ  
+
+  For more information, refer to
+
+https://rocmdocs.amd.com/en/latest/Programming_Guides/HIP-FAQ.html#hip-faq
+
+
+## ROCm Data Center User and API Guide
+
+* ROCm Data Center Tool User Guide
+
+   - Reliability, Accessibility, and Serviceability (RAS) Plugin Integration
+
+  For more information, refer to the ROCm Data Center User Guide at,
+
+https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_ROCm_DataCenter_Tool_User_Guide_v4.2.pdf
+  
+
+* ROCm Data Center Tool API Guide
+
+  For more information, refer to the ROCm Data Center API Guide at,
+
+https://github.com/RadeonOpenCompute/ROCm/blob/master/ROCm_Data_Center_Tool_API_Guide_v4.2.pdf
+
+
+## ROCm SMI API Documentation Updates 
+
+* ROCm SMI API Guide 
+
+  For more information, refer to the ROCm SMI API Guide at,
+
+ https://github.com/RadeonOpenCompute/ROCm/blob/master/ROCm_SMI_Manual_4.2.pdf
+  
+## ROC Debugger User and API Guide 
+
+* ROC Debugger User Guide 
+https://github.com/RadeonOpenCompute/ROCm/blob/master/ROCm_Debugger_User_Guide_v4.2.pdf
+
+  
+
+* Debugger API Guide 
+https://github.com/RadeonOpenCompute/ROCm/blob/master/ROCm_Debugger_API_Guide_v4.2.pdf  
 
-https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_ROCm_DataCenter_Tool_User_Guide.pdf
 
 ## General AMD ROCm Documentation Links
 
@@ -100,129 +193,320 @@ Access the following links for more information:
 
 * For AMD ROCm binary structure, see
 
-  https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html#build-amd-rocm
+  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/Installation_Guide/Installation-Guide.html#amd-rocm-version-history
+ https://rocmdocs.amd.com/en/latest/Current_Release_Notes/ROCm-Version-History.html
 
 
 
 # What\'s New in This Release
 
-## Hipfort-Interface for GPU Kernel Libraries
+## HIP Enhancements
 
-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 Target Platform Macro
+
+The platform macros are updated to target either the AMD or NVIDIA platform in HIP projects. They now include corresponding headers and libraries for compilation/linking.
+
+* *__HIP_PLATFORM_AMD__* is defined if the HIP platform targets AMD. Note, __HIP_PLATFORM_HCC__ was used previously if the HIP platform targeted AMD. 
+This is now deprecated.
+
+* *__HIP_PLATFORM_NVIDIA__* is defined if the HIP platform targets NVIDIA. Note, _HIP_PLATFORM_NVCC__  was used previously if the HIP platform targeted NVIDIA. This is now deprecated.
+
+For example,
+
+```
+
+	#if (defined(__HIP_PLATFORM_AMD__)) && !(defined(__HIP_PLATFORM_NVIDIA__))
+
+	#include <hip/amd_detail/hip_complex.h>
+
+	#elif !(defined(__HIP_PLATFORM_AMD__)) && (defined(__HIP_PLATFORM_NVIDIA__))
+
+	#include <hip/nvidia_detail/hip_complex.h>
+
+```
+
+### Updated HIP 'Include' Directories
+
+In the ROCm4.2 release, HIP *include* header directories for platforms are updated as follows:
+
+* *amd_detail/* - includes source header details for the ‘amd’ platform implementation. In previous releases, the "hcc_detail" directory was defined, and it it is now deprecated.  
+
+* *nvidia_detail/* - includes source header details for the ‘nvidia’ platform implementation. In previous releases, the "nvcc_detail" directory was defined, and it is now deprecated. 
+
+
+### HIP Stream Memory Operations
+
+The ROCm v4.2 extends support to Stream Memory Operations to enable direct synchronization between Network Nodes and GPU. The following new APIs are added:
+
+* hipStreamWaitValue32
+* hipStreamWaitValue64
+* hipStreamWriteValue32
+* hipStreamWriteValue64
+
+For more details, see the HIP API guide at
+
+https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_HIP_API_Guide_4.2.pdf
+
+
+### HIP Events in Kernel Dispatch
+
+HIP events in kernel dispatch using *hipExtLaunchKernelGGL/hipExtLaunchKernel* and passed in the API are not explicitly recorded and should only be used to get elapsed time for that specific launch.
+
+Events used across multiple dispatches, for example, start and stop events from different *hipExtLaunchKernelGGL/hipExtLaunchKernel* calls, are treated as invalid unrecorded events. In such scenarios, HIP will display the error *"hipErrorInvalidHandle"* from *hipEventElapsedTime*.
+
+For more details, refer to the HIP API Guide at
+
+https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_HIP_API_Guide_4.2.pdf
+
+
+### Changed Environment Variables for HIP
+
+In the ROCm v3.5 release, the Heterogeneous Compute Compiler (HCC) compiler was deprecated, and the HIP-Clang compiler was introduced for compiling Heterogeneous-Compute Interface for Portability (HIP) programs. In addition, the HIP runtime API was implemented on top of Radeon Open Compute Common Language Runtime (ROCclr). ROCclr is an abstraction layer that provides the ability to interact with different runtime backends such as ROCr.
+
+While the HIP_PLATFORM=hcc environment variable was functional in subsequent releases, in the ROCm v4.1 release, the following environment variables were changed:
+
+* *HIP_PLATFORM=hcc to HIP_PLATFORM=amd*
+
+* *HIP_PLATFORM=nvcc to HIP_PLATFORM=nvidia*
+
+Therefore, any applications continuing to use the HIP_PLATFORM=hcc variable will fail. You must update the environment variables to reflect the changes as mentioned above. 
 
-The hipfort interface library is meant for Fortran developers with a focus on gfortran users. 
 
-For information on HIPFort installation and examples, see
-https://github.com/ROCmSoftwarePlatform/hipfort
-  
 
 ## ROCm Data Center Tool 
 
-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:
+### RAS Integration
 
-* GPU telemetry  
+The ROCm Data Center (RDC) Tool is enhanced with the Reliability, Accessibility, and Serviceability (RAS) plugin. 
 
-* GPU statistics for jobs 
+For more information about RAS integration and installation, refer to the ROCm Data Center Tool User guide at:
 
-* Integration with third-party tools 
-
-* Open source 
-
-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. 
-
-![ScreenShot](https://github.com/Rmalavally/ROCm/blob/master/RDCComponentsrevised.png)
+https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_ROCm_DataCenter_Tool_User_Guide_v4.2.pdf
 
 
-Refer to the ROCm Data Center Tool™ User Guide for more details on the different modes of operation.  
+## ROCm Math and Communication Libraries 
 
-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. 
+### rocBLAS
 
-For installation information on different distributions, refer to the ROCm Data Center User Guide at
+Enhancements and fixes:
 
-https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_ROCm_DataCenter_Tool_User_Guide.pdf
+* Added option to install script to build only rocBLAS clients with a pre-built rocBLAS library
+
+* Supported gemm ext for unpacked int8 input layout on gfx908 GPUs
+
+   * Added new flags rocblas_gemm_flags::rocblas_gemm_flags_pack_int8x4 to specify if using the packed layout
+
+     * Set the rocblas_gemm_flags_pack_int8x4 when using packed int8x;, this should be always set on GPUs before gfx908
+
+     * For gfx908 GPUs, unpacked int8 is supported. Setting of this flag is no longer required
+
+     * Notice the default flags 0 uses unpacked int8 and changes the behaviour of int8 gemm from ROCm 4.1.0
+
+* Added a query function rocblas_query_int8_layout_flag to get the preferable layout of int8 for gemm by device
+
+For more information, refer to 
+
+https://rocblas.readthedocs.io/en/master/
 
 
-### Error Correcting Code Fields in ROCm Data Center Tool
+### rocRAND
 
-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. 
+* Performance fixes
 
-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. 
+For more information, refer to
 
-![ScreenShot](https://github.com/Rmalavally/ROCm/blob/master/forweb.PNG)
+https://rocrand.readthedocs.io/en/latest/
 
-## Static Linking Libraries 
 
-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.
+### rocSOLVER	
 
-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.
+Support for:
+
+* Multi-level logging functionality
+
+* Implementation of the Thin-SVD algorithm
+
+* Reductions of generalized symmetric- and hermitian-definite eigenproblems:
+
+   * SYGS2, SYGST (with batched and strided_batched versions)
+   * HEGS2, HEGST (with batched and strided_batched versions)
+
+* Symmetric and hermitian matrix eigensolvers:
+
+   * SYEV (with batched and strided_batched versions)
+   * HEEV (with batched and strided_batched versions)
+   
+* Generalized symmetric- and hermitian-definite eigensolvers:
+
+   * SYGV (with batched and strided_batched versions)
+   * HEGV (with batched and strided_batched versions)
+
+For more information, refer to
+
+https://rocsolver.readthedocs.io/en/latest/
+
+
+### rocSPARSE	
+
+Enhancements:
+
+* SpMM (CSR, COO)
+* Code coverage analysis
+
+For more information, refer to
+
+https://rocsparse.readthedocs.io/en/latest/usermanual.html#rocsparse-gebsrmv
+
+
+### hipSPARSE	
+
+Enhancements:
+
+* Generic API support, including SpMM (CSR, COO)
+* csru2csr, csr2csru
+
+For more information, refer to
+
+https://rocsparse.readthedocs.io/en/latest/usermanual.html#types
 
-In the AMD ROCm v3.8 release, the following libraries support static linking: 
 
-![ScreenShot](https://github.com/Rmalavally/ROCm/blob/master/staticlinkinglib.PNG)
 
 # Fixed Defects
-The following defects are fixed in this release:
 
-* 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
+## Performance Impact for LDS-BOUND Kernels 
+
+The following issue is fixed in the ROCm v4.2 release. 
+
+The compiler in ROCm v4.1 generates LDS load and stores instructions that incorrectly assume equal performance between aligned and misaligned accesses. While this does not impact code correctness, it may result in sub-optimal performance.
+
 
 # Known Issues 
 
-## Undefined Reference Issue in Statically Linked Libraries
+The following are the known issues in this release.
 
-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.  
+## Upgrade to AMD ROCm v4.2 Not Supported
 
-Client applications may require linking with an additional library -lgcc_s to resolve the undefined reference to symbol '_Unwind_Resume@@GCC_3.0'.
+An upgrade from previous releases to AMD ROCm v4.2 is not supported. Complete uninstallation of previous ROCm versions is required before installing a new version of ROCm.
 
-## MIGraphX Pooling Operation Fails for Some Models
+The hip-base package has a dependency on Perl modules that some operating systems may not have in their default package repositories.  Use the following commands to add repositories that have the required Perl packages:
 
-MIGraphX does not work for some models with pooling operations and the following error appears:
 
-*‘test_gpu_ops_test FAILED’*
+#### For SLES 15 SP2
 
-This issue is currently under investigation and there is no known workaround currently. 
+		sudo zypper addrepo 
 
-## MIVisionX Installation Error on CentOS/RHEL8.2 and SLES 15
 
-Installing ROCm on MIVisionX results in the following error on CentOS/RHEL8.2 and SLES 15:
+For more information, see
 
-*"Problem: nothing provides opencv needed"*
+https://download.opensuse.org/repositories/devel:languages:perl/SLE_15/devel:languages:perl.repo
 
-As a workaround, install opencv before installing MIVisionX.
+
+
+#### For CentOS8.3
+
+		sudo yum config-manager --set-enabled powertools
+	
+
+#### For RHEL8.3
+
+		sudo subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms
+ 
+ 
+## Modulefile Fails to Install Automatically in ROCm Multi-Version Environment
+
+The ROCm v4.2 release includes a preliminary implementation of environment modules to enable switching between multi versions of ROCm installation. The modulefile in */opt/rocm-4.2/lib/rocmmod* fails to install automatically in the ROCm multi-version environment.
+
+This is a known limitation for environment modules in ROCm, and the issue is under investigation at this time. 
+
+**Workaround**
+
+Ensure you install the modulefile in */opt/rocm-4.2/lib/rocmmod* manually in a multi-version installation environment. 
+
+For general information about modules, see
+http://modules.sourceforge.net/ 
+
+## Issue with Input/Output Types for Scan Algorithms in rocThrust
+
+As rocThrust is updated to match CUDA Thrust 1.10, the different input/output types for scan algorithms in rocThrust/CUDA Thrust are no longer officially supported.  In this situation, the current C++ standard does not specify the intermediate accumulator type leading to potentially incorrect results and ill-defined behavior. 
+
+As a workaround, users can:
+
+* Use the same types for input and output
+
+Or 
+
+* For exclusive_scan, explicitly specify an *InitialValueType* in the last argument
+
+Or 
+
+* For inclusive_scan, which does not have an initial value argument, use a transform_iterator  to explicitly cast the input iterators to match the output’s value_type
+
+
+## Precision Issue in AMD RADEON™ PRO VII and AMD RADEON™ VII
+
+In AMD Radeon™ Pro VII AND AMD Radeon™ VII, a precision issue can occur when using the Tensorflow XLA path.
+
+This issue is currently under investigation.
+
+
+
+# Deprecations
+
+This section describes deprecations and removals in AMD ROCm.
+
+## Compiler Generated Code Object Version 2 Deprecation 
+
+Compiler-generated code object version 2 is no longer supported and has been completely removed. Support for loading code object version 2 is also deprecated with no announced removal release.
 
 
 # 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/Installation-Guide.html#software-stack-for-amd-gpu
+
+
+
 # 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 +522,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 +565,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 +578,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 +611,17 @@ 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
 
-## Machine Learning and High Performance Computing Software Stack for AMD GPU
+AMD®, the AMD Arrow logo, AMD Instinct™, Radeon™, ROCm® and combinations thereof are trademarks of Advanced Micro Devices, Inc.
 
-For an updated version of the software stack for AMD GPU, see
+Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
+
+PCIe® is a registered trademark of PCI-SIG Corporation. Other product names used in this publication are for identification purposes only and may be trademarks of their respective companies.  
+
+Google®  is a registered trademark of Google LLC.
+
+Ubuntu and the Ubuntu logo are registered trademarks of Canonical Ltd.
+
+Other product names used in this publication are for identification purposes only and may be trademarks of their respective companies.
 
-https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html#software-stack-for-amd-gpu

default.xml

@@ -1,27 +1,27 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <manifest>
     <remote name="roc-github"
-            fetch="http://github.com/RadeonOpenCompute/" />
+fetch="http://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.2.0"
+     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="ROC-smi" revision="refs/tags/rocm-4.1.0" />
+    <project name="rocm_smi_lib" />
     <project name="rocm-cmake" />
     <project name="rocminfo" />
     <project name="rocprofiler" remote="rocm-devtools" />
@@ -29,26 +29,30 @@
     <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="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" remote="roc-github" />
     <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" />
@@ -62,18 +66,10 @@
     <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>