Remove inaccessible repos

Addition of ROCm release notes

README.md

@@ -1,245 +1,538 @@
-# AMD ROCm Release Notes v3.3.0
-This page describes the features, fixed issues, and information about downloading and installing the ROCm software.
-It also covers known issues and deprecated features in the ROCm v3.3 release.
+# AMD ROCm™ v4.1 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 the AMD ROCm v4.1 release.
 
-- [What Is ROCm?](#What-Is-ROCm)
-  * [ROCm Components](#ROCm-Components)
+- [Supported Operating Systems and Documentation Updates](#Supported-Operating-Systems-and-Documentation-Updates)
   * [Supported Operating Systems](#Supported-Operating-Systems)
-  * [Important ROCm Links](#Important-ROCm-Links)
-  
+  * [ROCm Installation Updates](#ROCm-Installation-Updates)
+  * [AMD ROCm Documentation Updates](#AMD-ROCm-Documentation-Updates)
+
+- [Driver Compatibility Issue in This Release](#Driver-Compatibility-Issue-in-This-Release)
+   
 - [What\'s New in This Release](#Whats-New-in-This-Release)
-  * [Multi Version Installation](#Multi-Version-Installation)
-  * [GPU Process Information](#GPU-Process-Information)
-  * [Support for 3D Pooling Layers](#Support-for-3D-Pooling-Layers)
-  * [ONNX Enhancements](#ONNX-Enhancements)
-  
-  
+  * [TargetID for Multiple Configurations](#TargetID-for-Multiple-Configurations)
+  * [ROCm Data Center Tool](#ROCm-Data-Center-Tool)
+  * [ROCm Math and Communication Libraries](#ROCm-Math-and-Communication-Libraries)
+  * [HIP Enhancements](#HIP-Enhancements)
+  * [OpenMP Enhancements and Fixes](#OpenMP-Enhancements-and-Fixes)
+  * [MIOpen Tensile Integration](#MIOpen-Tensile-Integration)
+
+    
+- [Known Issues](#Known-Issues)
+
+- [Deprecations](#Deprecations)
+
+  * [Compiler Generated Code Object Version 2 Deprecation ](#Compiler-Generated-Code-Object-Version-2-Deprecation)
+
 - [Deploying ROCm](#Deploying-ROCm)
  
-- [Deprecations in This Release](#Deprecations-in-This-Release)
-  * [Code Object Manager (Comgr) Functions](#Code-Object-Manager-(Comgr)-Functions)
-
-
 - [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)
   * [ROCm Binary Package Structure](#ROCm-Binary-Package-Structure)
   * [ROCm Platform Packages](#ROCm-Platform-Packages)
   
 
-## What Is ROCm?
-ROCm is designed to be a universal platform for gpu-accelerated computing. This modular design allows hardware vendors to build drivers that support the ROCm framework. ROCm is also designed to integrate multiple programming languages and makes it easy to add support for other languages. 
-
-Note: You can also clone the source code for individual ROCm components from the GitHub repositories.
 
 
-### ROCm Components
-The following components for the ROCm platform are released and available for the v3.3
-release:
+## ROCm Installation Updates 
 
-• Drivers
+### List of Supported Operating Systems
 
-• Tools
+The AMD ROCm platform is designed to support the following operating systems:
 
-• Libraries
+* Ubuntu 20.04.1 (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
 
-• Source Code
+### FRESH INSTALLATION OF AMD ROCM V4.1 RECOMMENDED
 
-You can access the latest supported version of drivers, tools, libraries, and source code for the ROCm platform at the following location:
-https://github.com/RadeonOpenCompute/ROCm
+A complete uninstallation of previous ROCm versions is required before installing a new version of ROCm. An upgrade from previous releases to AMD ROCm v4.1 is not supported. For more information, refer to the AMD ROCm Installation Guide at
 
-### Supported Operating Systems
-The ROCm v3.3.x platform is designed to support the following operating systems:
+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.
 
-* Ubuntu 16.04.6 (Kernel 4.15) and 18.04.4 (Kernel 5.3)
+**Note**: *render* group is required only for Ubuntu v20.04. For all other ROCm supported operating systems, continue to use video group. 
 
-* CentOS v7.7 (Using devtoolset-7 runtime support)
+* For ROCm v3.5 and releases thereafter, the clinfo path is changed to /opt/rocm/opencl/bin/clinfo. 
 
-* RHEL v7.7 (Using devtoolset-7 runtime support)
+* For ROCm v3.3 and older releases, the clinfo path remains /opt/rocm/opencl/bin/x86_64/clinfo. 
+ 
+### ROCM MULTI-VERSION INSTALLATION UPDATE
 
-* SLES 15 SP1 
+With the AMD ROCm v4.1 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.   
+
+* Version files must be created for each multi-version rocm <= 4.1.0
+
+ * Command: echo <version> | sudo tee /opt/rocm-<version>/.info/version
+
+ * Example: echo 4.1.0 | sudo tee /opt/rocm-4.1.0/.info/version
+
+* 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.
 
 
 
-### Important ROCm Links
+# Driver Compatibility Issue in This Release
 
-Access the following links for more information on:
+In certain scenarios, the ROCm 4.1 run-time and userspace environment are not compatible with ROCm v4.0 and older driver implementations for 7nm-based (Vega 20) hardware (MI50 and MI60). 
 
-* ROCm documentation, see 
-https://rocm-documentation.readthedocs.io/en/latest/index.html
+To mitigate issues, the ROCm v4.1 or newer userspace prevents running older drivers for these GPUs.
 
-* ROCm Release Notes
-https://rocm-documentation.readthedocs.io/en/latest/Current_Release_Notes/Current-Release-Notes.html
+Users are notified in the following scenarios:
 
-* ROCm QuickStart Installation Guide, see
-https://rocm-documentation.readthedocs.io/en/latest/Installation_Guide/Installation-Guide.html
+* Bare Metal 
+* Containers
+ 
+## Bare Metal
 
-* ROCm binary structure, see
-https://rocm-documentation.readthedocs.io/en/latest/Installation_Guide/Installation-Guide.html#rocm-platform-packages
+In the bare-metal environment, the following error message displays in the console: 
 
+*“HSA Error: Incompatible kernel and userspace, Vega 20 disabled. Upgrade amdgpu.”*
 
-* Instructions to install PyTorch after ROCm is installed – https://rocm-documentation.readthedocs.io/en/latest/Deep_learning/Deep-learning.html#pytorch
+To test the compatibility, run the ROCm v4.1 version of rocminfo using the following instruction: 
 
-Note: These instructions reference the rocm/pytorch:rocm3.0_ubuntu16.04_py2.7_pytorch image. However, you can substitute the Ubuntu 18.04 image listed at https://hub.docker.com/r/rocm/pytorch/tags
+*/opt/rocm-4.1.0/bin/rocminfo 2>&1 | less*
 
+## Containers
 
-## What\'s New in This Release
+A container (built with error detection for this issue) using a ROCm v4.1 or newer run-time is initiated to execute on an older kernel. The container fails to start and the following warning appears:
 
-### Multi Version Installation
+*Error: Incompatible ROCm environment. The Docker container requires the latest kernel driver to operate correctly.
+Upgrade the ROCm kernel to v4.1 or newer, or use a container tagged for v4.0.1 or older.*
 
-Users can install and access multiple versions of the ROCm toolkit simultaneously.
+To inspect the version of the installed kernel driver,  run either: 
 
-Previously, users could install only a single version of the ROCm toolkit. 
-
-Now, users have the option to install multiple versions simultaneously and toggle to the desired version of the ROCm toolkit. From the v3.3 release, multiple versions of ROCm packages can be installed in the */opt/rocm-<version>* folder. 
-
-
-**Prerequisites**
-
-Ensure the existing installations of ROCm, including/opt/rocm, are completely removed before the v3.3 ROCm toolkit installation. The ROCm v3.3 package requires a clean installation.
-
-* To install a single instance of ROCm, use the rocm-dkms or rocm-dev packages to install all the required components. This creates a symbolic link /opt/rocm pointing to the corresponding version of ROCm installed on the system. 
-
-* To install individual ROCm components, create the /opt/rocm symbolic link pointing to the version of ROCm installed on the system. 
-For example, # ln -s /opt/rocm-3.3.0 /opt/rocm
-
-* To install multiple instance ROCm packages, create /opt/rocm symbolic link pointing to the version of ROCm installed/used on the system. 
-For example, # ln -s /opt/rocm-3.3.0 /opt/rocm
-
-**NOTE**: The Kernel Fusion Driver (KFD) must be compatible with all versions of the ROCm software installed on the system.
-
-**Before You Begin**
-
-Review the following important notes:
-
-Single Version Installation
-
-To install a single instance of the ROCm package, access the non-versioned packages. You must not install any components from the multi-instance set.
-
-For example, 
-
-* rocm-dkms
-* rocm-dev
-* hip
-
-A fresh installation or an upgrade of the single-version installation will remove the existing version completely and install the new version in the */opt/rocm-<version>* folder.
-
-![ScreenShot](singleinstance.png)
-
-
-**Multi-version Installation**
-
-* To install a multi-instance of the ROCm package, access the versioned packages and components. 
-
-For example,
-
-* rocm-dkms3.3.0
-* rocm-dev3.3.0
-* hip3.3.0
-	
-* The new multi-instance package enables you to install two versions of the ROCm toolkit simultaneously and provides the ability to toggle between the two versioned packages.
-
-* The ROCm-DEV package does not create symlinks
-
-* Users must create symlinks if required
-
-* Multi-version installation with previous ROCm versions is not supported
-
-* Kernel Fusion Driver (KFD) must be compatible with all versions of ROCm installations
-
-![ScreenShot](MultiIns.png)
-
-**IMPORTANT**: A single instance ROCm package cannot co-exist with the multi-instance package. 
-
-**NOTE**: The multi-instance installation applies only to ROCm v3.3 and above. This package requires a fresh installation after the complete removal of existing ROCm packages. **The multi-version installation is not backward compatible.**
-
-
-## GPU Process Information 
-
-A new functionality to display process information for GPUs is available in this release. For example,  you can view the process details to determine if the GPU(s) must be reset. 
-
-To display the GPU process details, you can:
-
-* Invoke the API 
+* dpkg --status rock-dkms [Debian-based]
 
 or
 
-* Use the Command Line Interface (CLI)
+* rpm -ql rock-dkms [RHEL, SUSE, and others]
 
-For more details about the API and the command instructions, see
+To install or update the driver, follow the installation instructions at:
 
-https://github.com/RadeonOpenCompute/rocm_smi_lib/blob/master/docs/ROCm_SMI_Manual.pdf
+https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html
 
 
-## Support for 3D Pooling Layers
+# AMD ROCm Documentation Updates
 
-AMD ROCm is enhanced to include support for 3D pooling layers. The implementation of 3D pooling layers now allows users to run 3D convolutional networks, such as ResNext3D, on AMD Radeon Instinct GPUs. 
+## AMD ROCm Installation Guide 
+
+The AMD ROCm Installation Guide in this release includes:
+
+* Supported Environments
+
+* Installation Instructions for v4.1
+
+* HIP Installation Instructions 
+
+For more information, refer to the ROCm documentation website at:
+
+https://rocmdocs.amd.com/en/latest/
 
 
-## ONNX Enhancements
+## AMD ROCm - HIP Documentation Updates
+
+* HIP Programming Guide v4.1 
+
+  https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_HIP_Programming_Guide_v4.1.pdf
+
+* HIP API Guide v4.1
+
+  https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_HIP_API_Guide_v4.1.pdf
+  
+
+* HIP-Supported CUDA API Reference Guide v4.1
+
+  https://github.com/RadeonOpenCompute/ROCm/blob/master/HIP_Supported_CUDA_API_Reference_Guide_v4.1.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
+
+   - Grafana 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.1.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_Manual_4.1.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_API_GUIDE_v4.1.pdf
+  
+## ROC Debugger User and API Guide 
+
+* ROC Debugger User Guide 
+
+  https://github.com/RadeonOpenCompute/ROCm/blob/master/Debugging%20with%20ROCGDB%20User%20Guide%20v4.1.pdf
+  
+
+* Debugger API Guide 
+
+  https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD-Debugger%20API%20Guide%20v4.1.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/Software-Stack-for-AMD-GPU.html
+  
+
+* For AMD ROCm Release History, see
+
+ https://rocmdocs.amd.com/en/latest/Current_Release_Notes/ROCm-Version-History.html
+
+
+
+# What\'s New in This Release
+
+## TARGETID FOR MULTIPLE CONFIGURATIONS
+
+The new TargetID functionality allows compilations to specify various configurations of the supported hardware. 
+
+Previously, ROCm supported only a single configuration per target. 
+
+With the TargetID enhancement, ROCm supports configurations for Linux, PAL and associated configurations such as XNACK. This feature addresses configurations for the same target in different modes and allows applications to build executables that specify the supported configurations, including the option to be agnostic for the desired setting.
+
+
+### New Code Object Format Version for TargetID
+
+* A new clang option -mcode-object-version can be used to request the legacy code object version 3 or code object version 2. For more information, refer to
+
+  https://llvm.org/docs/AMDGPUUsage.html#elf-code-object
+
+* A new clang --offload-arch= option is introduced to specify the offload target architecture(s) for the HIP language.
+
+* The clang --offload-arch= and -mcpu options accept a new Target ID syntax. This allows both the processor and target feature settings to be specified. For more details, refer to
+
+  https://llvm.org/docs/AMDGPUUsage.html#amdgpu-target-id
+
+    - If a target feature is not specified, it defaults to a new concept of "any". The compiler, then, produces code, 
+      which executes on a target configured for either value of the setting impacting the overall performance. 
+      
+      It is recommended to explicitly specify the setting for more efficient performance. 
+
+    - In particular, the setting for XNACK now defaults to produce less performant code than previous ROCm releases.
+
+    - The legacy clang -mxnack, -mno-xnack, -msram-ecc, and -mno-sram-ecc options are deprecated. They are still 
+      supported, however, they will be removed in a future release. 
+
+    - The new Target ID syntax renames the SRAM ECC feature from sram-ecc to sramecc.
+
+* The clang offload bundler uses the new offload hipv4 for HIP code object version 4. For more information, see 
+https://clang.llvm.org/docs/ClangOffloadBundler.html
+
+* ROCm v4.1 corrects code object loading to enforce target feature settings of the code object to match the setting of the agent. It also corrects the recording of target feature settings in the code object. As a consequence, the legacy code objects may no longer load due to mismatches.
+
+* gfx802, gfx803, and gfx805 do not support the XNACK target feature in the ROCm v4.1 release.
+
+
+### New Code Object Tools
+
+AMD ROCm v4.1 provides new code object tools *roc-obj-ls* and *roc-obj-extract*. These tools allow for the listing and extraction of AMD GPU ROCm code objects that are embedded in HIP executables and shared objects. Each tool supports a --help option that provides more information. 
+
+Refer to the HIP Programming Guide v4.1 for additional information and examples.
+
+https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_HIP_Programming_Guide_v4.1.pdf
+
+**Note**
+
+The extractkernel tool in previous AMD ROCm releases has been removed from the AMD ROCm v4.1 release 
+and will no longer be  supported.
+
+**Note**
  
-Open Neural Network eXchange (ONNX) is a widely-used neural net exchange format. The AMD model compiler & optimizer support the pre-trained models in ONNX, NNEF, & Caffe formats. Currently, ONNX versions 1.3 and below are supported. 
+ The roc-obj-ls and roc-obj-extract tools may generate an error about the following missing Perl modules: 
 
-The AMD Neural Net Intermediate Representation (NNIR) is enhanced to handle the rapidly changing ONNX versions and its layers. 
+* File::Which
+* File::BaseDir
+* File::Copy
+* URI::Encode
 
-![ScreenShot](onnx.png)
+This error is due to the missing dependencies in the hip-base installer package.  As a workaround, you may use the 
+following instructions to install the Perl modules:  
 
-For more details about AMD support for ONNX and ISV samples, see
-
-https://github.com/GPUOpen-ProfessionalCompute-Libraries/MIVisionX/tree/master/model_compiler
+*Ubuntu*
+     
+     apt-get install libfile-which-perl libfile-basedir-perl libfile-copy-recursive-perl liburi-encode-perl
+   
+*CentOS*
+            
+      yum install “ perl(File::Which) perl(File::BaseDir) perl(File::Copy) perl(URI::Encode)
 
 
 
-## Deploying ROCm
-AMD hosts both Debian and RPM repositories for the ROCm v3.3.0x packages. 
+## ROCm Data Center Tool 
 
-The following directions show how to install ROCm on supported Debian-based systems such as Ubuntu 18.04.x. 
+### Grafana Integration
 
-Note: These directions may not work as written on unsupported Debian-based distributions. For example, newer versions of Ubuntu may not be compatible with the rock-dkms kernel driver. In this case, you can exclude the rocm-dkms and rock-dkms packages.
+The ROCm Data Center (RDC) Tool is enhanced with the Grafana plugin. Grafana is a common monitoring stack used for storing and visualizing time series data. Prometheus acts as the storage backend, and Grafana is used as the interface for analysis and visualization. Grafana has a plethora of visualization options and can be integrated with Prometheus for the ROCm Data Center (RDC) dashboard. 
+
+For more information about Grafana integration and installation, refer to the ROCm Data Center Tool User guide at:
+
+https://github.com/RadeonOpenCompute/ROCm/blob/master/AMD_ROCm_DataCenter_Tool_User_Guide_v4.1.pdf
+
+
+
+## ROCm Math and Communication Libraries 
+
+### rocSPARSE
+
+rocSPARSE extends support for:
+
+* gebsrmm
+* gebsrmv
+* gebsrsv
+* coo2dense and dense2coo
+* generic API including axpby, gather, scatter, rot, spvv, spmv, spgemm, sparsetodense, densetosparse
+* mixed indexing types in matrix formats
+
+For more information, see 
+
+https://rocsparse.readthedocs.io/en/latest/
+
+
+### rocSOLVER
+
+rocSOLVER extends support for:
+
+* Eigensolver routines for symmetric/hermitian matrices:
+  - STERF, STEQR
+  
+* Linear solvers for general non-square systems:
+  - GELS (API added with batched and strided_batched versions. Only the overdetermined non-transpose case is implemented in 
+    this release. Other cases will return rocblas_status_not_implemented status for now.)
+    
+* Extended test coverage for functions returning information
+
+* Changelog file
+
+* Tridiagonalization routines for symmetric and hermitian matrices:
+  - LATRD
+  - SYTD2, SYTRD (with batched and strided_batched versions)
+  - HETD2, HETRD (with batched and strided_batched versions)
+  
+* Sample code and unit test for unified memory model/Heterogeneous Memory Management (HMM)
+
+For more information, see
+
+https://rocsolver.readthedocs.io/en/latest/
+
+### hipCUB
+
+The new iterator DiscardOutputIterator in hipCUB represents a special kind of pointer that ignores values written to it upon dereference.  It is useful for ignoring the output of certain algorithms without wasting memory capacity or bandwidth.  DiscardOutputIterator may also be used to count the size of an algorithm's output, which was not known previously.
+
+For more information, see
+
+https://hipcub.readthedocs.io/en/latest/
+
+
+## HIP Enhancements
+
+### Support for hipEventDisableTiming Flag
+
+HIP now supports the hipEventDisableTiming flag for hipEventCreateWithFlags. Note, events created with this flag do not record profiling data and provide optimal performance when used for synchronization.
+
+### Cooperative Group Functions
+
+Cooperative Groups defines, synchronizes, and communicates between groups of threads and blocks for efficiency and ease of management. HIP now supports the following kernel language Cooperative Groups types and functions:
+
+![Screenshot](https://github.com/Rmalavally/ROCm/blob/master/images/CG1.PNG)
+![Screenshot](https://github.com/Rmalavally/ROCm/blob/master/images/CG2.PNG)
+![Screenshot](https://github.com/Rmalavally/ROCm/blob/master/images/CG3.PNG)
+
+
+###  Support for Extern Shared Declarations
+
+Previously, it was required to declare dynamic shared memory using the HIP_DYNAMIC_SHARED macro for accuracy as using static shared memory in the same kernel could result in overlapping memory ranges and data-races.
+Now, the HIP-Clang compiler provides support for extern shared declarations, and the HIP_DYNAMIC_SHARED option is no longer required. 
+
+You may use the standard extern definition:
+
+    extern __shared__ type var[];
+
+
+## OpenMP Enhancements and Fixes
+
+This release includes the following OpenMP changes:
+
+* Usability Enhancements
+* Fixes to Internal Clang Math Headers
+* OpenMP Defect Fixes
+
+### Usability Enhancements
+
+* OMPD updates for flang
+* To support OpenMP debugging, the selected OpenMP runtime sources are included in lib-debug/src/openmp. The ROCgdb debugger 
+  will find these automatically.
+* Threadsafe hsa plugin for libomptarget
+* Support multiple devices with malloc and hostrpc
+* Improve hostrpc version check
+* Add max reduction offload feature to flang
+* Integration of changes to support HPC Toolkit
+* Support for fprintf
+* Initial support for GPU malloc and Free. The internal (device rtl) is required for GPU malloc and Free for nested parallelism.  
+  GPU malloc and Free are now replaced, which improves the device memory footprint.
+* Increase detail of debug printing controlled by LIBOMPTARGET_KERNEL_TRACE environment variable
+* Add support for -gpubnames in Flang Driver
+* Increase detail of debug printing controlled by LIBOMPTARGET_KERNEL_TRACE environment variable
+* Add support for -gpubnames in Flang Driver
+
+###  Fixes to Internal Clang Math Headers
+
+This release includes a set of changes applied to Clang internal headers to support OpenMP C, C++, FORTRAN, and HIP C. This establishes consistency between NVPTX and AMDGCN offloading, and OpenMP, HIP, and CUDA. OpenMP uses function variants and header overlays to define device versions of functions. This causes Clang LLVM IR codegen to mangle names of variants in both the definition and callsites of functions defined in the internal Clang headers. The changes apply to headers found in the installation subdirectory lib/clang/11.0.0/include.
+
+The changes also temporarily eliminate the use of the libm bitcode libraries for C and C++. Although math functions are now defined with internal clang headers, a bitcode library of the C functions defined in the headers is still built for the FORTRAN toolchain linking. This is because FORTRAN cannot use C math headers. This bitcode library is installed in lib/libdevice/libm-.bc. The source build of the bitcode library is implemented with the aomp-extras repository and the component-built script build_extras.sh. 
+
+### OpenMP Defect Fixes
+
+The following OpenMP defects are fixed in this release:
+
+* Openmpi configuration issue with real16. 
+* [flang] The AOMP 11.7-1 Fortran compiler claims to support the -isystem flag, but ignores it.
+* [flang] producing internal compiler error when the character is used with KIND.
+* [flang] openmp map clause on complex allocatable expressions !$omp target data map( chunk%tiles(1)%field%density0).
+* Add a fatal error if missing -Xopenmp-target or -march options when -fopenmp-targets is specified. However, this requirement is not 
+  applicable for offloading to the host when there is only a single target and that target is the host.
+* Openmp error message output for no_rocm_device_lib was asserting.
+* Linkage on constant per-kernel symbols from external to weaklinkageonly to prevent duplicate symbols when building kokkos.
+* Add environment variables ROCM_LLD_ARGS ROCM_LINK_ARGS ROCM_SELECT_ARGS to test driver options without compiler rebuild.  
+* Fix problems with device math functions being ambiguous, especially the pow function.ix aompcc to accept file type cxx. 
+* Fix a latent race between host runtime and devicertl.
+
+## MIOPEN TENSILE INTEGRATION
+
+MIOpenTensile provides host-callable interfaces to the Tensile library and supports the HIP programming model. You may use the Tensile feature in the HIP backend by setting the building environment variable value to ON.
+
+    MIOPEN_USE_MIOPENTENSILE=ON
+
+MIOpenTensile is an open-source collaboration tool where external entities can submit source pull requests (PRs) for updates. MIOpenTensile maintainers review and approve the PRs using standard open-source practices. 
+
+For more information about the sources and the build system, see
+
+https://github.com/ROCmSoftwarePlatform/MIOpenTensile
+
+
+# Known Issues 
+
+The following are the known issues in this release.
+
+## Upgrade to AMD ROCm v4.1 Not Supported
+
+An upgrade from previous releases to AMD ROCm v4.1 is not supported. A complete uninstallation of previous ROCm versions is required before installing a new version of ROCm.
+
+## Performance Impact for Kernel Launch Bound Attribute
+
+Kernels without the *__launch_bounds__* attribute assume the default maximum threads per block value. In the previous ROCm release, this value was 256. In the ROCm v4.1 release, it is changed to 1024. The objective of this change ensures the actual threads per block value used to launch a kernel, by default, are always within the launch bounds, thus, establishing the correctness of HIP programs. 
+
+**NOTE**: Using the above-mentioned approach may incur performance degradation in certain cases. Users must add a minimum launch bound to each kernel, which covers all possible threads per block values used to launch that kernel for correctness and performance. 
+
+The recommended workaround to recover the performance is to add *--gpu-max-threads-per-block=256* to the compilation options for HIP programs.
+
+## Issue with Passing a Subset of GPUs in a Multi-GPU System
+
+ROCm support for passing individual GPUs via the docker --device flag in a Docker run command has a known issue when passing a subset of GPUs in a multi-GPU system. The command runs without any warning or error notification. However, all GPU executable run outputs are randomly corrupted. 
+
+Using GPU targeting via the Docker command is not recommended for users of ROCm 4.1. There is no workaround for this issue currently. 
+
+## Performance Impact for LDS-Bound Kernels
+
+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.
+
+This issue is under investigation, and there is no known workaround at this time.
+
+
+# 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 packages. 
 
 For more information on ROCM installation on all platforms, see
 
-https://rocm-documentation.readthedocs.io/en/latest/Installation_Guide/Installation-Guide.html
+https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html
 
 
-## Deprecations in This Release
+# Machine Learning and High Performance Computing Software Stack for AMD GPU
 
-### Code Object Manager (Comgr) Functions
+For an updated version of the software stack for AMD GPU, see
 
-The following Code Object Manager (Comgr) functions are deprecated.
-
-* `amd_comgr_action_info_set_options` 
-
-* `amd_comgr_action_info_get_options` 
-
-These functions were originally deprecated in version 1.3 of the Comgr library as they no longer support options with embedded spaces. 
-The deprecated functions are now replaced with the array-oriented options API, which includes 
-
-* `amd_comgr_action_info_set_option_list`
-
-* `amd_comgr_action_info_get_option_list_count`
-
-* `amd_comgr_action_info_get_option_list_item`
+https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html#software-stack-for-amd-gpu
 
 
-## Hardware and Software Support
+
+# 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
@@ -252,10 +545,10 @@ As described in the next section, GFX8 GPUs require PCI Express 3.0 (PCIe 3.0) w
 
 The integrated GPUs in AMD APUs are not officially supported targets for ROCm.
 As described [below](#limited-support), "Carrizo", "Bristol Ridge", and "Raven Ridge" APUs are enabled in our upstream drivers and the ROCm OpenCL runtime.
-However, they are not enabled in our HCC or HIP runtimes, and may not work due to motherboard or OEM hardware limitations.
+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.
@@ -295,26 +588,29 @@ does not require or take advantage of PCIe Atomics. However, we still recommend
 from the list provided above for compatibility purposes.
 
 #### Not supported or limited support under ROCm
+
 ##### 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 HCC, HIP, or our libraries built on top of these compilers and runtimes.
+* 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.
   * In addition, various "Carrizo" and "Bristol Ridge" platforms may not work due to OEM and ODM choices when it comes to key configurations parameters such as inclusion of the required CRAT tables and IOMMU configuration parameters in the system BIOS.
   * Before purchasing such a system for ROCm, please verify that the BIOS provides an option for enabling IOMMUv2 and that the system BIOS properly exposes the correct CRAT table. Inquire with your vendor about the latter.
-* AMD "Raven Ridge" APUs are enabled to run OpenCL, but do not yet support HCC, HIP, or our libraries built on top of these compilers and runtimes.
+* AMD "Raven 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, "Raven Ridge" requires the use of upstream kernel drivers.
   * In addition, various "Raven Ridge" platforms may not work due to OEM and ODM choices when it comes to key configurations parameters such as inclusion of the required CRAT tables and IOMMU configuration parameters in the system BIOS.
   * Before purchasing such a system for ROCm, please verify that the BIOS provides an option for enabling IOMMUv2 and that the system BIOS properly exposes the correct CRAT table. Inquire with your vendor about the latter.
 
 ##### Not supported
 
-* "Tonga", "Iceland", "Vega M", and "Vega 12" GPUs are not supported in ROCm 2.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.
@@ -341,211 +637,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 |
 
 
-## Software Support
-As of AMD ROCm v1.9.0, the ROCm user-level software is compatible with the AMD drivers in certain upstream Linux kernels. You have the following options:
+# Disclaimer
 
-• Use the ROCk kernel driver that is a part of AMD’s ROCm repositories 
-or
-• Use the upstream driver and only install ROCm user-level utilities from AMD’s ROCm repositories
+AMD®, the AMD Arrow logo, AMD Instinct™, Radeon™, ROCm® and combinations thereof are trademarks of Advanced Micro Devices, Inc.
 
-The releases of the upstream Linux kernel support the following GPUs in ROCm:
+Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
 
-• Fiji, Polaris 10, Polaris 11
-• Fiji, Polaris 10, Polaris 11, Vega10
-• Fiji, Polaris 10, Polaris 11, Vega10, Vega 7nm
+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.
 
-## Machine Learning and High Performance Computing Software Stack for AMD GPU
+Other product names used in this publication are for identification purposes only and may be trademarks of their respective companies.
 
-ROCm Version 3.3.0
-
-### ROCm Binary Package Structure
-
- ROCm is a collection of software ranging from drivers and runtimes to libraries and developer tools.
-In AMD's package distributions, these software projects are provided as a separate packages.
-This allows users to install only the packages they need, if they do not wish to install all of ROCm.
-These packages will install most of the ROCm software into `/opt/rocm/` by default.
-
-The packages for each of the major ROCm components are:
-
-* ROCm Core Components
-  - ROCk Kernel Driver: `rock-dkms`
-  - ROCr Runtime: `hsa-rocr-dev`, `hsa-ext-rocr-dev`
-  - ROCt Thunk Interface: `hsakmt-roct`, `hsakmt-roct-dev`
-* ROCm Support Software
-  - ROCm SMI: `rocm-smi`
-  - ROCm cmake: `rocm-cmake`
-  - rocminfo: `rocminfo`
-  - ROCm Bandwidth Test: `rocm_bandwidth_test`
-* ROCm Development Tools
-  - HCC compiler: `hcc`
-  - HIP: `hip_base`, `hip_doc`, `hip_hcc`, `hip_samples`
-  - ROCm Device Libraries: `rocm-device-libs`
-  - ROCm OpenCL: `rocm-opencl`, `rocm-opencl-devel` (on RHEL/CentOS), `rocm-opencl-dev` (on Ubuntu)
-  - ROCM Clang-OCL Kernel Compiler: `rocm-clang-ocl`
-  - Asynchronous Task and Memory Interface (ATMI): `atmi`
-  - ROCr Debug Agent: `rocr_debug_agent`
-  - ROCm Code Object Manager: `comgr`
-  - ROC Profiler: `rocprofiler-dev`
-  - ROC Tracer: `roctracer-dev`
-  - Radeon Compute Profiler: `rocm-profiler`
-* ROCm Libraries
-  - rocALUTION: `rocalution`
-  - rocBLAS: `rocblas`
-  - hipBLAS: `hipblas`
-  - hipCUB: `hipCUB`
-  - rocFFT: `rocfft`
-  - rocRAND: `rocrand`
-  - rocSPARSE: `rocsparse`
-  - hipSPARSE: `hipsparse`
-  - ROCm SMI Lib: `rocm_smi_lib64`
-  - rocThrust: `rocThrust`
-  - MIOpen: `MIOpen-HIP` (for the HIP version), `MIOpen-OpenCL` (for the OpenCL version)
-  - MIOpenGEMM: `miopengemm`
-  - MIVisionX: `mivisionx`
-  - RCCL: `rccl`
-
-To make it easier to install ROCm, the AMD binary repositories provide a number of meta-packages that will automatically install multiple other packages.
-For example, `rocm-dkms` is the primary meta-package that is used to install most of the base technology needed for ROCm to operate.
-It will install the `rock-dkms` kernel driver, and another meta-package (`rocm-dev`) which installs most of the user-land ROCm core components, support software, and development tools.
-
-The `rocm-utils` meta-package will install useful utilities that, while not required for ROCm to operate, may still be beneficial to have.
-Finally, the `rocm-libs` meta-package will install some (but not all) of the libraries that are part of ROCm.
-
-The chain of software installed by these meta-packages is illustrated below
-
-```
-  rocm-dkms
-    |--rock-dkms
-    \--rocm-dev
-       |--comgr
-       |--hcc
-       |--hip_base
-       |--hip_doc
-       |--hip_hcc
-       |--hip_samples
-       |--hsakmt-roct
-       |--hsakmt-roct-dev
-       |--hsa-amd-aqlprofile
-       |--hsa-ext-rocr-dev
-       |--hsa-rocr-dev
-       |--rocm-cmake
-       |--rocm-device-libs
-       |--rocm-smi
-       |--rocprofiler-dev
-       |--rocr_debug_agent
-       \--rocm-utils
-          |--rocminfo
-          \--rocm-clang-ocl # This will cause OpenCL to be installed
-
-  rocm-libs
-    |--hipblas
-    |--hipcub
-    |--hipsparse
-    |--rocalution
-    |--rocblas
-    |--rocfft
-    |--rocprim
-    |--rocrand
-    |--rocsparse
-    \--rocthrust
-```
-
-These meta-packages are not required but may be useful to make it easier to install ROCm on most systems.
-
-Note:Some users may want to skip certain packages. For instance, a user that wants to use the upstream kernel drivers (rather than those supplied by AMD) may want to skip the `rocm-dkms` and `rock-dkms` packages, and instead directly install `rocm-dev`.
-
-Similarly, a user that only wants to install OpenCL support instead of HCC and HIP may want to skip the `rocm-dkms` and `rocm-dev` packages. Instead, they could directly install `rock-dkms`, `rocm-opencl`, and `rocm-opencl-dev` and their dependencies.
-
-
-### ROCm Platform Packages
-
-Drivers, ToolChains, Libraries, and Source Code 
-
-The latest supported version of the drivers, tools, libraries and source code for the ROCm platform have been released and are available from the following GitHub repositories:
-
-#### ROCm Core Components
-  - [ROCk Kernel Driver](https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/tree/roc-3.3.0)
-  - [ROCr Runtime](https://github.com/RadeonOpenCompute/ROCR-Runtime/tree/rocm-3.3.0)
-  - [ROCT Thunk Interface](https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface/tree/roc-3.3.0)  
-
-  
-#### ROCm Support Software
-  - [ROCm SMI](https://github.com/RadeonOpenCompute/ROC-smi/tree/roc-3.3.0)
-  - [ROCm cmake](https://github.com/RadeonOpenCompute/rocm-cmake/tree/rocm-3.3.0)
-  - [rocminfo](https://github.com/RadeonOpenCompute/rocminfo/tree/rocm-3.3.0)
-  - [ROCm Bandwidth Test](https://github.com/RadeonOpenCompute/rocm_bandwidth_test/tree/rocm-3.3.0)
-  
-#### ROCm Development ToolChains
-  - [HCC compiler](https://github.com/RadeonOpenCompute/hcc/tree/rocm-hcc-3.3.0)
-  
-  - [HIP](https://github.com/ROCm-Developer-Tools/HIP/tree/rocm-3.3.0)
-  
-  - [ROCm Device Libraries HCC](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/roc-ocl-3.3.0)
-  
-  - [ROCm OpenCL Runtime](http://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime/tree/roc-3.3.0)
-   
-  - [ROCm LLVM OCL](http://github.com/RadeonOpenCompute/llvm-project/tree/rocm-ocl-3.3.0)   
-      
-  - [ROCm Device Libraries OCL](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/rocm-ocl-3.3.0)
-      
-  - [ROCM Clang-OCL Kernel Compiler](https://github.com/RadeonOpenCompute/clang-ocl/tree/rocm-3.3.0)
-  
-  - [Asynchronous Task and Memory Interface (ATMI)](https://github.com/RadeonOpenCompute/atmi/tree/rocm-3.3.0)
-  
-  - [ROCr Debug Agent](https://github.com/ROCm-Developer-Tools/rocr_debug_agent/tree/roc-3.3.0)
-  
-  - [ROCm Code Object Manager](https://github.com/RadeonOpenCompute/ROCm-CompilerSupport/tree/rocm-3.3.0)
-  
-  - [ROC Profiler](https://github.com/ROCm-Developer-Tools/rocprofiler/tree/roc-3.3.0)
-  
-  - [ROC Tracer](https://github.com/ROCm-Developer-Tools/roctracer/tree/roc-3.3.0)
-  
-  - [AOMP](https://github.com/ROCm-Developer-Tools/aomp/tree/roc-3.3.0)
-  
-  - [Radeon Compute Profiler](https://github.com/GPUOpen-Tools/RCP/tree/3a49405)
-  
-  - [ROCmValidationSuite](https://github.com/ROCm-Developer-Tools/ROCmValidationSuite/tree/roc-3.3.0)
-  
-  - Example Applications:
-    - [HCC Examples](https://github.com/ROCm-Developer-Tools/HCC-Example-Application/tree/ffd65333)
-    
-    - [HIP Examples](https://github.com/ROCm-Developer-Tools/HIP-Examples/tree/rocm-3.3.0)
-    
-#### ROCm Libraries
-
-  - [rocBLAS](https://github.com/ROCmSoftwarePlatform/rocBLAS/tree/rocm-3.3.0)
-  
-  - [hipBLAS](https://github.com/ROCmSoftwarePlatform/hipBLAS/tree/rocm-3.3.0)
-  
-  - [rocFFT](https://github.com/ROCmSoftwarePlatform/rocFFT/tree/rocm-3.3)
-  
-  - [rocRAND](https://github.com/ROCmSoftwarePlatform/rocRAND/tree/rocm-3.3.0)
-  
-  - [rocSPARSE](https://github.com/ROCmSoftwarePlatform/rocSPARSE/tree/rocm-3.3.0)
-  
-  - [hipSPARSE](https://github.com/ROCmSoftwarePlatform/hipSPARSE/tree/rocm-3.3.0)
-  
-  - [rocALUTION](https://github.com/ROCmSoftwarePlatform/rocALUTION/tree/rocm-3.3.0)
-  
-  - [MIOpenGEMM](https://github.com/ROCmSoftwarePlatform/MIOpenGEMM/tree/b51a125)
-  
-  - [MIOpen](https://github.com/ROCmSoftwarePlatform/MIOpen/tree/roc-3.3.0)
-  
-  - [rocThrust](https://github.com/ROCmSoftwarePlatform/rocThrust/tree/rocm-3.3.0)
-  
-  - [ROCm SMI Lib](https://github.com/RadeonOpenCompute/rocm_smi_lib/tree/rocm-3.3.0)
-  
-  - [RCCL](https://github.com/ROCmSoftwarePlatform/rccl/tree/rocm-3.3.0)
-  
-  - [MIVisionX](https://github.com/GPUOpen-ProfessionalCompute-Libraries/MIVisionX/commit/755e7a08d5299a95c42def092af7c736d5eda90c)
-  
-  - [MIVisionX] https://github.com/GPUOpen-ProfessionalCompute-Libraries/MIVisionX/tree/1.7)
-  
-  - [hipCUB](https://github.com/ROCmSoftwarePlatform/hipCUB/tree/rocm-3.3.0)
-  
-  - [AMDMIGraphX](https://github.com/ROCmSoftwarePlatform/AMDMIGraphX/commit/d1e945dabce0078d44c78de67b00232b856e18bc)
-
-
-Features and enhancements introduced in previous versions of ROCm can be found in [version_history.md](version_history.md)

default.xml

@@ -1,85 +1,74 @@
 <?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/" />
-
-    <default revision="refs/tags/rocm-3.3.0"
-             remote="roc-github"
-             sync-c="true"
-             sync-j="4" />
-
-    <project name="ROCK-Kernel-Driver" revision="refs/tags/roc-3.3.0" />
-    <project name="ROCT-Thunk-Interface" revision="refs/tags/roc-3.3.0" />
+fetch="https://github.com/GPUOpen-Tools/" />
+    <remote name="KhronosGroup"
+fetch="https://github.com/KhronosGroup/" />
+    <default revision="refs/tags/rocm-4.1.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" revision="refs/tags/roc-3.3.0" />
-    <project name="rocm_smi_lib" remote="roc-github" />
+    <project name="ROC-smi" />
+    <project name="rocm_smi_lib" />
     <project name="rocm-cmake" />
     <project name="rocminfo" />
-
-    <project name="rocprofiler" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
-    <project name="roctracer" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
-    <!-- If you want to get the full OpenCL runtime, there is a separate repo
-         manifest that is more authoritative than the copy in this file. It can
-         be found at the following URL:
-         https://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime/blob/roc-2.0.0/opencl.xml -->
-    <remote name="KhronosGroup" fetch="https://github.com/KhronosGroup/" />
-    <project name="ROCm-OpenCL-Runtime" revision="refs/tags/roc-3.3.0" />
-
+    <project name="rocprofiler" remote="rocm-devtools" />
+    <project name="roctracer" remote="rocm-devtools" />
+    <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" />
-    <!-- HCC needs to be recursively synced to get it submodules -->
-    <project name="hcc" sync-s="true" />
-    <project name="HCC-Example-Application" remote="rocm-devtools" revision="ffd6533305e79eed667badd3c4cdb7879a1281b8" />
+<!--HIP Projects-->
     <project name="HIP" remote="rocm-devtools" />
     <project name="HIP-Examples" remote="rocm-devtools" />
-
-    <!-- The following projects are all associated with the AMDGPU LLVM compiler -->
-    <project name="llvm-project" path="llvm_amd-stg-open" revision="refs/tags/rocm-ocl-3.3.0"/>
-    <project name="ROCm-Device-Libs" revision="refs/tags/rocm-ocl-3.3.0"/>
-    <project name="atmi" revision="refs/tags/rocm-3.3.0" />
+    <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" />
+    <project name="ROCm-Device-Libs" />
+    <project name="atmi" />
     <project name="ROCm-CompilerSupport" />
-    <project name="rocr_debug_agent" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
+    <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" />
-
-    <!-- ROCm Libraries -->
+<!-- gdb projects -->
+    <project name="ROCgdb" remote="rocm-devtools" />
+    <project name="ROCdbgapi" remote="rocm-devtools" />
+<!-- 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" revision="refs/tags/rocm-3.3" />
+    <project name="rocFFT" remote="rocm-swplat" />
     <project name="rocRAND" remote="rocm-swplat" />
     <project name="rocSPARSE" remote="rocm-swplat" />
+    <project name="rocSOLVER" remote="rocm-swplat" />
     <project name="hipSPARSE" remote="rocm-swplat" />
     <project name="rocALUTION" remote="rocm-swplat" />
-    <project name="MIOpenGEMM" remote="rocm-swplat" revision="b51a12523676451bf38bfcf0506a0745e80ac64f" />
-    <project name="MIOpen" remote="rocm-swplat" revision="refs/tags/roc-3.3.0" />
+    <project name="MIOpenGEMM" remote="rocm-swplat" />
+    <project name="MIOpen" remote="rocm-swplat" />
     <project name="rccl" remote="rocm-swplat" />
-    <project name="MIVisionX" remote="gpuopen-libs" revision="refs/tags/1.7" />
+    <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="AMDMIGraphX" remote="rocm-swplat" revision="d1e945dabce0078d44c78de67b00232b856e18bc" />
-    <project name="ROCmValidationSuite" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
-
-    <!-- Projects for AOMP -->
-    <project name="ROCT-Thunk-Interface" path="aomp/roct-thunk-interface" remote="roc-github" revision="refs/tags/roc-3.3.0" />
-    <project name="ROCR-Runtime" path="aomp/rocr-runtime" remote="roc-github" revision="refs/tags/rocm-3.3.0" />
-    <project name="hcc" path="aomp/hcc" remote="roc-github" revision="6776c83ff233bbc53d8e5e4185c2e53e400bef6f" />
-    <project name="ROCm-Device-Libs" path="aomp/rocm-device-libs" remote="roc-github" revision="fea23ca22221ef2228d043d2e6b8ab00c8b8d60d" />
-    <project name="ROCm-CompilerSupport" path="aomp/rocm-compilersupport" remote="roc-github" revision="d970a94c2d0f6f481a1bcbe7c9f0995443a75893" />
-    <project name="rocminfo" path="aomp/rocminfo" remote="roc-github" revision="70ebe13a8932944bc8d369cc7a91d6e2c0c8e65f" />
-    <project name="atmi" path="aomp/atmi" remote="roc-github" revision="b8cbdb710fee1776d8f7d8299e8acfdd62cbaaaf" />
-    <project name="HIP" path="aomp/hip" remote="rocm-devtools" revision="83a42c24d8e719b29e4b965d7d71ce43fa9c07e2" />
-    <project name="aomp" path="aomp/aomp" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
-    <project name="aomp-extras" path="aomp/aomp-extras" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
-    <project name="flang" path="aomp/flang" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
-    <project name="llvm-project" path="aomp/llvm-project" remote="rocm-devtools" revision="refs/tags/roc-aomp-3.3.0" />
+    <project name="hipfort" remote="rocm-swplat" />
+    <project name="AMDMIGraphX" remote="rocm-swplat" />
+    <project name="ROCmValidationSuite" remote="rocm-devtools" />
+<!-- Projects for OpenMP-Extras -->
+    <project name="aomp" path="openmp-extras/aomp" remote="rocm-devtools" />
+    <project name="aomp-extras" path="openmp-extras/aomp-extras" remote="rocm-devtools" />
+    <project name="flang" path="openmp-extras/flang" remote="rocm-devtools" />
 </manifest>

version_history.md

@@ -1,503 +0,0 @@
-## ROCm Version History
-This file contains archived version history information for the [ROCm project](https://github.com/RadeonOpenCompute/ROCm)
-
-### Current ROCm Version: 3.3
-- [New features and enhancements in ROCm v3.1](#new-features-and-enhancements-in-rocm-v31)
-- [New features and enhancements in ROCm v3.0](#new-features-and-enhancements-in-rocm-v30)
-- [New features and enhancements in ROCm v2.10](#new-features-and-enhancements-in-rocm-v210)
-- [New features and enhancements in ROCm 2.9](#new-features-and-enhancements-in-rocm-29)
-- [New features and enhancements in ROCm 2.8](#new-features-and-enhancements-in-rocm-28)
-- [New features and enhancements in ROCm 2.7.2](#new-features-and-enhancements-in-rocm-272)
-- [New features and enhancements in ROCm 2.7](#new-features-and-enhancements-in-rocm-27)
-- [New features and enhancements in ROCm 2.6](#new-features-and-enhancements-in-rocm-26)
-- [New features and enhancements in ROCm 2.5](#new-features-and-enhancements-in-rocm-25)
-- [New features and enhancements in ROCm 2.4](#new-features-and-enhancements-in-rocm-24)
-- [New features and enhancements in ROCm 2.3](#new-features-and-enhancements-in-rocm-23)
-- [New features and enhancements in ROCm 2.2](#new-features-and-enhancements-in-rocm-22)
-- [New features and enhancements in ROCm 2.1](#new-features-and-enhancements-in-rocm-21)
-- [New features and enhancements in ROCm 2.0](#new-features-and-enhancements-in-rocm-20)
-- [New features and enhancements in ROCm 1.9.2](#new-features-and-enhancements-in-rocm-192)
-- [New features and enhancements in ROCm 1.9.2](#new-features-and-enhancements-in-rocm-192-1)
-- [New features and enhancements in ROCm 1.9.1](#new-features-and-enhancements-in-rocm-191)
-- [New features and enhancements in ROCm 1.9.0](#new-features-and-enhancements-in-rocm-190)
-- [New features as of ROCm 1.8.3](#new-features-as-of-rocm-183)
-- [New features as of ROCm 1.8](#new-features-as-of-rocm-18)
-- [New Features as of ROCm 1.7](#new-features-as-of-rocm-17)
-- [New Features as of ROCm 1.5](#new-features-as-of-rocm-15)
-
-
-## New features and enhancements in ROCm v3.2
-The AMD ROCm v3.2 release was not productized.
-
-## New features and enhancements in ROCm v3.1
-### Change in ROCm Installation Directory Structure
-
-A fresh installation of the ROCm toolkit installs the packages in the /opt/rocm-<version> folder. Previously, ROCm toolkit packages were installed in the /opt/rocm folder.
-
-### Reliability, Accessibility, and Serviceability Support for Vega 7nm
-
-The Reliability, Accessibility, and Serviceability (RAS) support for Vega7nm is now available.
-
-### SLURM Support for AMD GPU
-
-SLURM (Simple Linux Utility for Resource Management) is an open source, fault-tolerant, and highly scalable cluster management and job scheduling system for large and small Linux clusters.
-
-
-## New features and enhancements in ROCm v3.0
-### Support for CentOS RHEL v7.7 <a id="centos-anchor"></a> 
-Support is extended for CentOS/RHEL v7.7 in the ROCm v3.0 release. For more information about the CentOS/RHEL v7.7 release, see:
-
-[CentOS/RHEL](https://centos.org/forums/viewtopic.php?t=71657)
-
-
-### Initial distribution of AOMP 0.7-5 in ROCm v3.0 <a id="aomp-anchor"></a> 
-The code base for this release of AOMP is the Clang/LLVM 9.0 sources as of October 8th, 2019. The LLVM-project branch used to build this release is AOMP-191008. It is now locked. With this release, an artifact tarball of the entire source tree is created. This tree includes a Makefile in the root directory used to build AOMP from the release tarball. You can use Spack to build AOMP from this source tarball or build manually without Spack.
-
-For more information about AOMP 0.7-5, see: [AOMP](https://github.com/ROCm-Developer-Tools/aomp/tree/roc-3.0.0)
-
-
-### Fast Fourier Transform Updates
-The Fast Fourier Transform (FFT) is an efficient algorithm for computing the Discrete Fourier Transform. Fast Fourier transforms are used in signal processing, image processing, and many other areas. The following real FFT performance change is made in the ROCm v3.0 release:
-
-•	Implement efficient real/complex 2D transforms for even lengths.
-
-Other improvements:
-
-•	More 2D test coverage sizes.
-
-•	Fix buffer allocation error for large 1D transforms.
-
-•	C++ compatibility improvements.
-
-### MemCopy Enhancement for rocProf
-In the v3.0 release, the rocProf tool is enhanced with an additional capability to dump asynchronous GPU memcopy information into a .csv file. You can use the '-hsa-trace' option to create the results_mcopy.csv file.
-Future enhancements will include column labels.
-
-
-### New features and enhancements in ROCm v2.10
-#### rocBLAS Support for Complex GEMM
-The rocBLAS library is a gpu-accelerated implementation of the standard Basic Linear Algebra Subroutines (BLAS). rocBLAS is designed to enable you to develop algorithms, including high performance computing, image analysis, and machine learning.
-
-In the AMD ROCm release v2.10, support is extended to the General Matrix Multiply (GEMM) routine for multiple small matrices processed simultaneously for rocBLAS in AMD Radeon Instinct MI50. Both single and double precision, CGEMM and ZGEMM, are now supported in rocBLAS.
-
-#### Support for SLES 15 SP1
-In the AMD ROCm v2.10 release, support is added for SUSE Linux® Enterprise Server (SLES) 15 SP1. SLES is a modular operating system for both multimodal and traditional IT.
-
-#### Code Marker Support for rocProfiler and rocTracer Libraries
-Code markers provide the external correlation ID for the calling thread. This function indicates that the calling thread is entering and leaving an external API region.
-
-### New features and enhancements in ROCm 2.9
-
-#### Initial release for Radeon Augmentation Library(RALI)
-The AMD Radeon Augmentation Library (RALI) is designed to efficiently decode and process images from a variety of storage formats and modify them through a processing graph programmable by the user. RALI currently provides C API.
-
-#### Quantization in MIGraphX v0.4
-MIGraphX 0.4 introduces support for fp16 and int8 quantization. For additional details, as well as other new MIGraphX features, see [MIGraphX documentation](https://github.com/ROCmSoftwarePlatform/AMDMIGraphX/wiki/Getting-started:-using-the-new-features-of-MIGraphX-0.4).
-
-#### rocSparse csrgemm
-csrgemm enables the user to perform matrix-matrix multiplication with two sparse matrices in CSR format.
-
-#### Singularity Support
-ROCm 2.9 adds support for Singularity container version 2.5.2.
-
-#### Initial release of rocTX
-ROCm 2.9 introduces rocTX, which provides a C API for code markup for performance profiling.  This initial release of rocTX supports annotation of code ranges and ASCII markers.  For an example, see this [code](https://github.com/ROCm-Developer-Tools/roctracer/blob/amd-master/test/MatrixTranspose_test/MatrixTranspose.cpp).
-
-#### Added support for Ubuntu 18.04.3
-Ubuntu 18.04.3 is now supported in ROCm 2.9.
-
-
-
-### New features and enhancements in ROCm 2.8
-
-#### Support for NCCL2.4.8 API
-Implements ncclCommAbort() and ncclCommGetAsyncError() to match the NCCL 2.4.x API
-
-### New features and enhancements in ROCm 2.7.2
-
-This release is a hotfix for ROCm release 2.7.
-
-#### Issues fixed in ROCm 2.7.2
-
-##### A defect in upgrades from older ROCm releases has been fixed.
-
-##### rocprofiler --hiptrace and --hsatrace fails to load roctracer library
-In ROCm 2.7.2, rocprofiler --hiptrace and --hsatrace fails to load roctracer library defect has been fixed.  
-To generate traces, please provide directory path also using the parameter: -d <$directoryPath> for example:
-```shell
-/opt/rocm/bin/rocprof  --hsa-trace -d $PWD/traces /opt/rocm/hip/samples/0_Intro/bit_extract/bit_extract
-  ```
-All traces and results will be saved under $PWD/traces path
-
-#### Upgrading from ROCm 2.7 to 2.7.2
-
-To upgrade, please remove 2.7 completely as specified [for ubuntu](#how-to-uninstall-from-ubuntu-1604-or-Ubuntu-1804) or [for centos/rhel](#how-to-uninstall-rocm-from-centosrhel-76), and install 2.7.2 as per instructions [install instructions](#installing-from-amd-rocm-repositories)
-
-#### Other notes
-
-  To use rocprofiler features, the following steps need to be completed before using rocprofiler:
-
-  ##### Step-1: Install roctracer
-
-###### Ubuntu 16.04 or Ubuntu 18.04:
-
-  ```shell
-  sudo apt install roctracer-dev
-  ```
-
-######  CentOS/RHEL 7.6:
-
-  ```shell
-  sudo yum install roctracer-dev
-  ```
-  ##### Step-2: Add /opt/rocm/roctracer/lib to LD_LIBRARY_PATH
-  
-### New features and enhancements in ROCm 2.7
-
-#### [rocFFT] Real FFT Functional
-Improved real/complex 1D even-length transforms of unit stride. Performance improvements of up to 4.5x are observed. Large problem sizes should see approximately 2x.
-
-#### rocRand Enhancements and Optimizations
-- Added support for new datatypes: uchar, ushort, half.
-- Improved performance on "Vega 7nm" chips, such as on the Radeon Instinct MI50
-- mtgp32 uniform double performance changes due generation algorithm standardization. Better quality random numbers now generated with 30% decrease in performance
-- Up to 5% performance improvements for other algorithms
-
-#### RAS
-Added support for RAS on Radeon Instinct MI50, including:
-- Memory error detection
-- Memory error detection counter
-
-#### ROCm-SMI enhancements
-Added ROCm-SMI CLI and LIB support for FW version, compute running processes, utilization rates, utilization counter, link error counter, and unique ID.
-
-### New features and enhancements in ROCm 2.6
-
-#### ROCmInfo enhancements
-ROCmInfo was extended to do the following:
-For ROCr API call errors including initialization determine if the error could be explained by:
-- ROCk (driver) is not loaded / available
-- User does not have membership in appropriate group - "video"
-- If not above print the error string that is mapped to the returned error code
-- If no error string is available, print the error code in hex
-
-#### Thrust - Functional Support on Vega20
-ROCm2.6 contains the first official release of rocThrust and hipCUB. rocThrust is a port of thrust, a parallel algorithm library. hipCUB is a port of CUB, a reusable software component library. Thrust/CUB has been ported to the HIP/ROCm platform to use the rocPRIM library. The HIP ported library works on HIP/ROCm platforms.
-
-Note: rocThrust and hipCUB library replaces https://github.com/ROCmSoftwarePlatform/thrust (hip-thrust), i.e. hip-thrust has been separated into two libraries, rocThrust and hipCUB. Existing hip-thrust users are encouraged to port their code to rocThrust and/or hipCUB. Hip-thrust will be removed from official distribution later this year.
-
-#### MIGraphX v0.3
-MIGraphX optimizer adds support to read models frozen from Tensorflow framework. Further details and an example usage at https://github.com/ROCmSoftwarePlatform/AMDMIGraphX/wiki/Getting-started:-using-the-new-features-of-MIGraphX-0.3
-
-#### MIOpen 2.0
-- This release contains several new features including an immediate mode for selecting convolutions, bfloat16 support, new layers, modes, and algorithms.
-- MIOpenDriver, a tool for benchmarking and developing kernels is now shipped with MIOpen.
-BFloat16 now supported in HIP requires an updated rocBLAS as a GEMM backend.
-- Immediate mode API now provides the ability to quickly obtain a convolution kernel.
-- MIOpen now contains HIP source kernels and implements the ImplicitGEMM kernels. This is a new feature and is currently disabled by default. Use the environmental variable "MIOPEN_DEBUG_CONV_IMPLICIT_GEMM=1" to activation this feature. ImplicitGEMM requires an up to date HIP version of at least 1.5.9211.
-- A new "loss" catagory of layers has been added, of which, CTC loss is the first. See the API reference for more details.
-2.0 is the last release of active support for gfx803 architectures. In future releases, MIOpen will not actively debug and develop new features specifically for gfx803.
-- System Find-Db in memory cache is disabled by default. Please see build instructions to enable this feature.
-Additional documentation can be found here: https://rocmsoftwareplatform.github.io/MIOpen/doc/html/
-
-#### Bloat16 software support in rocBLAS/Tensile
-Added mixed precision bfloat16/IEEE f32 to gemm_ex. The input and output matrices are bfloat16. All arithmetic is in IEEE f32.
-
-#### AMD Infinity Fabric™ Link enablement
-The ability to connect four Radeon Instinct MI60 or Radeon Instinct MI50 boards in two hives or two Radeon Instinct MI60 or Radeon Instinct MI50 boards in four hives via AMD Infinity Fabric™ Link GPU interconnect technology has been added.
-
-#### ROCm-smi features and bug fixes
-  - mGPU & Vendor check
-  - Fix clock printout if DPM is disabled
-  - Fix finding marketing info on CentOS
-  - Clarify some error messages
-
-#### ROCm-smi-lib enhancements
-- Documentation updates
-- Improvements to *name_get functions
-
-#### RCCL2 Enablement
-RCCL2 supports collectives intranode communication using PCIe, Infinity Fabric™, and pinned host memory, as well as internode communication using Ethernet (TCP/IP sockets) and Infiniband/RoCE (Infiniband Verbs).  Note: For Infiniband/RoCE, RDMA is not currently supported.
-
-#### rocFFT enhancements
-- Added: Debian package with FFT test, benchmark, and sample programs
-- Improved: hipFFT interfaces
-- Improved: rocFFT CPU reference code, plan generation code and logging code
-
-### New features and enhancements in ROCm 2.5
-
-#### UCX 1.6 support
-Support for UCX version 1.6 has been added.
-
-#### BFloat16 GEMM in rocBLAS/Tensile
-Software support for BFloat16 on Radeon Instinct MI50, MI60 has been added.  This includes:
-- Mixed precision GEMM with BFloat16 input and output matrices, and all arithmetic in IEEE32 bit
-- Input matrix values are converted from BFloat16 to IEEE32 bit, all arithmetic and accumulation is IEEE32 bit. Output values are rounded from IEEE32 bit to BFloat16
-- Accuracy should be correct to 0.5 ULP
-
-#### ROCm-SMI enhancements
-CLI support for querying the memory size, driver version, and firmware version has been added to ROCm-smi.
-
-#### [PyTorch] multi-GPU functional support (CPU aggregation/Data Parallel)
-Multi-GPU support is enabled in PyTorch using Dataparallel path for versions of PyTorch built using the 06c8aa7a3bbd91cda2fd6255ec82aad21fa1c0d5 commit or later.
-
-#### rocSparse optimization on Radeon Instinct MI50 and MI60
-This release includes performance optimizations for csrsv routines in the rocSparse library.
-
-#### [Thrust] Preview
-Preview release for early adopters. rocThrust is a port of thrust, a parallel algorithm library. Thrust has been ported to the HIP/ROCm platform to use the rocPRIM library. The HIP ported library works on HIP/ROCm platforms.
-
-Note: This library will replace https://github.com/ROCmSoftwarePlatform/thrust in a future release. The package for rocThrust (this library) currently conflicts with version 2.5 package of thrust. They should not be installed together.
-
-#### Support overlapping kernel execution in same HIP stream
-HIP API has been enhanced to allow independent kernels to run in parallel on the same stream.
-
-#### AMD Infinity Fabric&#x2122; Link enablement
-The ability to connect four Radeon Instinct MI60 or Radeon Instinct MI50 boards in one hive via AMD Infinity Fabric™ Link GPU interconnect technology has been added.
-### New features and enhancements in ROCm 2.4
-
-#### TensorFlow 2.0 support
-ROCm 2.4 includes the enhanced compilation toolchain and a set of bug fixes to support TensorFlow 2.0 features natively
-
-#### AMD Infinity Fabric&#x2122; Link enablement
-ROCm 2.4 adds support to connect two Radeon Instinct MI60 or Radeon Instinct MI50 boards via AMD Infinity Fabric&#x2122; Link GPU interconnect technology.
-
-### New features and enhancements in ROCm 2.3
-
-#### Mem usage per GPU
-Per GPU memory usage is added to rocm-smi.
-Display information regarding used/total bytes for VRAM, visible VRAM and GTT, via the --showmeminfo flag
-
-#### MIVisionX, v1.1 - ONNX
-ONNX parser changes to adjust to new file formats
-
-#### MIGraphX, v0.2
-MIGraphX 0.2 supports the following new features:
-* New Python API
-* Support for additional ONNX operators and fixes that now enable a large set of Imagenet models
-* Support for RNN Operators
-* Support for multi-stream Execution
-* [Experimental] Support for Tensorflow frozen protobuf files
-
-See: [Getting-started:-using-the-new-features-of-MIGraphX-0.2](https://github.com/ROCmSoftwarePlatform/AMDMIGraphX/wiki/Getting-started:-using-the-new-features-of-MIGraphX-0.2) for more details
-
-#### MIOpen, v1.8 - 3d convolutions and int8
-* This release contains full 3-D convolution support and int8 support for inference.
-* Additionally, there are major updates in the performance database for major models including those found in Torchvision.
-
-See: [MIOpen releases](https://github.com/ROCmSoftwarePlatform/MIOpen/releases)
-
-#### Caffe2 -  mGPU support
-Multi-gpu support is enabled for Caffe2.
-
-#### rocTracer library, ROCm tracing API for collecting runtimes API and asynchronous GPU activity traces
-HIP/HCC domains support is introduced in rocTracer library.
-
-#### BLAS -  Int8 GEMM performance, Int8 functional and performance
-Introduces support and performance optimizations for Int8 GEMM, implements TRSV support, and includes improvements and optimizations with Tensile.
-
-#### Prioritized L1/L2/L3 BLAS (functional)
-Functional implementation of BLAS L1/L2/L3 functions
-
-#### BLAS - tensile optimization
-Improvements and optimizations with tensile
-
-#### MIOpen Int8 support
-Support for int8
-
-### New features and enhancements in ROCm 2.2
-
-#### rocSparse Optimization on Vega20
-Cache usage optimizations for csrsv (sparse triangular solve), coomv
-(SpMV in COO format) and ellmv (SpMV in ELL format) are available.
-
-#### DGEMM and DTRSM Optimization
-Improved DGEMM performance for reduced matrix sizes (k=384, k=256)
-
-#### Caffe2
-Added support for multi-GPU training
-
-### New features and enhancements in ROCm 2.1
-
-#### RocTracer v1.0 preview release – 'rocprof' HSA runtime tracing and statistics support -
-Supports HSA API tracing and HSA asynchronous GPU activity including kernels execution and memory copy
-
-#### Improvements to ROCM-SMI tool -
-Added support to show real-time PCIe bandwidth usage via the -b/--showbw flag
-
-#### DGEMM Optimizations -
-Improved DGEMM performance for large square and reduced matrix sizes (k=384, k=256)
-
-### New features and enhancements in ROCm 2.0
-
-#### Adds support for RHEL 7.6 / CentOS 7.6 and Ubuntu 18.04.1
-
-#### Adds support for Vega 7nm, Polaris 12 GPUs
-
-#### Introduces MIVisionX
-* A comprehensive computer vision and machine intelligence libraries, utilities and applications bundled into a single toolkit.
-
-#### Improvements to ROCm Libraries
-* rocSPARSE & hipSPARSE
-* rocBLAS with improved DGEMM efficiency on Vega 7nm
-
-#### MIOpen
-* This release contains general bug fixes and an updated performance database
-* Group convolutions backwards weights performance has been improved
-* RNNs now support fp16
-
-#### Tensorflow multi-gpu and Tensorflow FP16 support for Vega 7nm
-* TensorFlow v1.12 is enabled with fp16 support
-
-#### PyTorch/Caffe2 with Vega 7nm Support
-* fp16 support is enabled
-* Several bug fixes and performance enhancements
-* Known Issue: breaking changes are introduced in ROCm 2.0 which are not addressed upstream yet. Meanwhile, please continue to use ROCm fork at https://github.com/ROCmSoftwarePlatform/pytorch
-
-#### Improvements to ROCProfiler tool
-* Support for Vega 7nm
-
-#### Support for hipStreamCreateWithPriority
-* Creates a stream with the specified priority. It creates a stream on which enqueued kernels have a different priority for execution compared to kernels enqueued on normal priority streams. The priority could be higher or lower than normal priority streams.
-
-#### OpenCL 2.0 support
-* ROCm 2.0 introduces full support for kernels written in the OpenCL 2.0 C language on certain devices and systems.  Applications can detect this support by calling the “clGetDeviceInfo” query function with “parame_name” argument set to “CL_DEVICE_OPENCL_C_VERSION”.  In order to make use of OpenCL 2.0 C language features, the application must include the option “-cl-std=CL2.0” in options passed to the runtime API calls responsible for compiling or building device programs.  The complete specification for the OpenCL 2.0 C language can be obtained using the following link: https://www.khronos.org/registry/OpenCL/specs/opencl-2.0-openclc.pdf
-
-#### Improved Virtual Addressing (48 bit VA) management for Vega 10 and later GPUs
-* Fixes Clang AddressSanitizer and potentially other 3rd-party memory debugging tools with ROCm
-* Small performance improvement on workloads that do a lot of memory management
-* Removes virtual address space limitations on systems with more VRAM than system memory
-
-#### Kubernetes support
-
-### New features and enhancements in ROCm 1.9.2
-#### RDMA(MPI) support on Vega 7nm
-* Support ROCnRDMA based on Mellanox InfiniBand
-
-#### Improvements to HCC
-* Improved link time optimization
-
-#### Improvements to ROCProfiler tool
-* General bug fixes and implemented versioning APIs
-
-### New features and enhancements in ROCm 1.9.2
-#### RDMA(MPI) support on Vega 7nm
-* Support ROCnRDMA based on Mellanox InfiniBand
-
-#### Improvements to HCC
-* Improved link time optimization
-
-#### Improvements to ROCProfiler tool
-* General bug fixes and implemented versioning APIs
-
-#### Critical bug fixes
-
-### New features and enhancements in ROCm 1.9.1
-#### Added DPM support to Vega 7nm
-* Dynamic Power Management feature is enabled on Vega 7nm.
-
-#### Fix for 'ROCm profiling' that used to fail with a “Version mismatch between HSA runtime and libhsa-runtime-tools64.so.1” error
-
-### New features and enhancements in ROCm 1.9.0
-
-#### Preview for Vega 7nm
-* Enables developer preview support for Vega 7nm
-
-#### System Management Interface
-* Adds support for the ROCm SMI (System Management Interface) library, which provides monitoring and management capabilities for AMD GPUs.
-
-#### Improvements to HIP/HCC
-* Support for gfx906
-* Added deprecation warning for C++AMP.  This will be the last version of HCC supporting C++AMP.
-* Improved optimization for global address space pointers passing into a GPU kernel
-* Fixed several race conditions in the HCC runtime
-* Performance tuning to the unpinned copy engine
-* Several codegen enhancement fixes in the compiler backend
-
-#### Preview for rocprof Profiling Tool
-Developer preview (alpha) of profiling tool rocProfiler. It includes a command-line front-end, `rpl_run.sh`, which enables:
-* Cmd-line tool for dumping public per kernel perf-counters/metrics and kernel timestamps
-* Input file with counters list and kernels selecting parameters
-* Multiple counters groups and app runs supported
-* Output results in CSV format
-
-The tool can be installed from the `rocprofiler-dev` package. It will be installed into: `/opt/rocm/bin/rpl_run.sh`
-
-#### Preview for rocr Debug Agent rocr_debug_agent
-The ROCr Debug Agent is a library that can be loaded by ROCm Platform Runtime to provide the following functionality:
-* Print the state for wavefronts that report memory violation or upon executing a "s_trap 2" instruction.
-* Allows SIGINT (`ctrl c`) or SIGTERM (`kill -15`) to print wavefront state of aborted GPU dispatches.
-* It is enabled on Vega10 GPUs on ROCm1.9.
-
-The ROCm1.9 release will install the ROCr Debug Agent library at `/opt/rocm/lib/librocr_debug_agent64.so`
-
-
-#### New distribution support
-
-* Binary package support for Ubuntu 18.04
-
-#### ROCm 1.9 is ABI compatible with KFD in upstream Linux kernels.
-Upstream Linux kernels support the following GPUs in these releases:
-4.17: Fiji, Polaris 10, Polaris 11
-4.18: Fiji, Polaris 10, Polaris 11, Vega10
-
-Some ROCm features are not available in the upstream KFD:
-* More system memory available to ROCm applications
-* Interoperability between graphics and compute
-* RDMA
-* IPC
-
-To try ROCm with an upstream kernel, install ROCm as normal, but do not install the rock-dkms package. Also add a udev rule to control `/dev/kfd` permissions:
-
-```
-    echo 'SUBSYSTEM=="kfd", KERNEL=="kfd", TAG+="uaccess", GROUP="video"' | sudo tee /etc/udev/rules.d/70-kfd.rules
-```
-
-### New features as of ROCm 1.8.3
-
-* ROCm 1.8.3 is a minor update meant to fix compatibility issues on Ubuntu releases running kernel 4.15.0-33
-
-### New features as of ROCm 1.8
-
-#### DKMS driver installation
-
- * Debian packages are provided for DKMS on Ubuntu
- * RPM packages are provided for CentOS/RHEL 7.4 and 7.5 support
- * See the [ROCT-Thunk-Interface](https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface/tree/roc-1.8.x) and [ROCK-Kernel-Driver](https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/tree/roc-1.8.x) for additional documentation on driver setup
-
-#### New distribution support
-
- * Binary package support for Ubuntu 16.04 and 18.04
- * Binary package support for CentOS 7.4 and 7.5
- * Binary package support for RHEL 7.4 and 7.5
-
-#### Improved OpenMPI via UCX support
-
- * UCX support for OpenMPI
- * ROCm RDMA
-
-### New Features as of ROCm 1.7
-
-#### DKMS driver installation
-
- * New driver installation uses Dynamic Kernel Module Support (DKMS)
- * Only amdkfd and amdgpu kernel modules are installed to support AMD hardware
- * Currently only Debian packages are provided for DKMS (no Fedora suport available)
- * See the [ROCT-Thunk-Interface](https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface/tree/roc-1.7.x) and [ROCK-Kernel-Driver](https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/tree/roc-1.7.x) for additional documentation on driver setup
-
-### New Features as of ROCm 1.5
-
-#### Developer preview of the new OpenCL 1.2 compatible language runtime and compiler
-
- * OpenCL 2.0 compatible kernel language support with OpenCL 1.2 compatible
-   runtime
- * Supports offline ahead of time compilation today;
-   during the Beta phase we will add in-process/in-memory compilation.
-
-#### Binary Package support for Ubuntu 16.04
-
-#### Binary Package support for Fedora 24 is not currently available
-
-#### Dropping binary package support for Ubuntu 14.04, Fedora 23
-
-#### IPC support