Update README.md

Update version_history.md
Update README.md
2026-01-09 22:58:17 -05:00 · 2020-04-01 16:16:14 -07:00 · 2020-04-01 16:00:18 -07:00 · 2020-04-01 15:58:27 -07:00 · 2020-04-01 15:49:26 -07:00 · 2020-04-01 18:41:52 -04:00
7 changed files with 1113 additions and 412 deletions
--- a/AMD_ROCm_Release_Notes_v3.3.pdf
+++ b/AMD_ROCm_Release_Notes_v3.3.pdf
--- a/MultiIns.png
+++ b/MultiIns.png
--- a/README.md
+++ b/README.md
@@ -1,411 +1,551 @@
-## Are You Ready to ROCK?
-The ROCm Platform brings a rich foundation to advanced computing by seamlessly
- integrating the CPU and GPU with the goal of solving real-world problems.
+# 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.
+
+- [What Is ROCm?](#What-Is-ROCm)
+  * [ROCm Components](#ROCm-Components)
+  * [Supported Operating Systems](#Supported-Operating-Systems)
+  * [Important ROCm Links](#Important-ROCm-Links)
+  
+- [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)
+  
+  
+- [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:
+
+• Drivers
+
+• Tools
+
+• Libraries
+
+• Source Code
+
+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
+
+### Supported Operating Systems
+The ROCm v3.3.x platform is designed to support the following operating systems:
+
+
+* Ubuntu 16.04.6 (Kernel 4.15) and 18.04.4 (Kernel 5.3)
+
+* CentOS v7.7 (Using devtoolset-7 runtime support)
+
+* RHEL v7.7 (Using devtoolset-7 runtime support)
+
+* SLES 15 SP1 
+
+
+
+### Important ROCm Links
+
+Access the following links for more information on:
+
+* ROCm documentation, see 
+https://rocm-documentation.readthedocs.io/en/latest/index.html
+
+* ROCm Release Notes
+https://rocm-documentation.readthedocs.io/en/latest/Current_Release_Notes/Current-Release-Notes.html
+
+* ROCm QuickStart Installation Guide, see
+https://rocm-documentation.readthedocs.io/en/latest/Installation_Guide/Installation-Guide.html
+
+* ROCm binary structure, see
+https://rocm-documentation.readthedocs.io/en/latest/Installation_Guide/Installation-Guide.html#rocm-platform-packages
+
+
+* Instructions to install PyTorch after ROCm is installed – https://rocm-documentation.readthedocs.io/en/latest/Deep_learning/Deep-learning.html#pytorch
+
+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
+
+
+## What\'s New in This Release
+
+### Multi Version Installation
+
+Users can install and access multiple versions of the ROCm toolkit simultaneously.
+
+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 
+
+or
+
+* Use the Command Line Interface (CLI)
+
+For more details about the API and the command instructions, see
+
+https://github.com/RadeonOpenCompute/rocm_smi_lib/blob/master/docs/ROCm_SMI_Manual.pdf
+
+
+## Support for 3D Pooling Layers
+
+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. 
+
+
+## ONNX Enhancements
+ 
+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 AMD Neural Net Intermediate Representation (NNIR) is enhanced to handle the rapidly changing ONNX versions and its layers. 
+
+![ScreenShot](onnx.png)
+
+For more details about AMD support for ONNX and ISV samples, see
+
+https://github.com/GPUOpen-ProfessionalCompute-Libraries/MIVisionX/tree/master/model_compiler
+
+
+
+## Deploying ROCm
+AMD hosts both Debian and RPM repositories for the ROCm v3.3.0x packages. 
+
+The following directions show how to install ROCm on supported Debian-based systems such as Ubuntu 18.04.x. 
+
+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.
+
+For more information on ROCM installation on all platforms, see
+
+https://rocm-documentation.readthedocs.io/en/latest/Installation_Guide/Installation-Guide.html
+
+
+## Deprecations in This Release
+
+### Code Object Manager (Comgr) Functions
+
+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`
+
+
+## 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.
+
+#### Supported GPUs
+Because the ROCm Platform has a focus on particular computational domains, we offer official support for a selection of AMD GPUs that are designed to offer good performance and price in these domains.
+
+ROCm officially supports AMD GPUs that use following chips:
+
+  * GFX8 GPUs
+    * "Fiji" chips, such as on the AMD Radeon R9 Fury X and Radeon Instinct MI8
+    * "Polaris 10" chips, such as on the AMD Radeon RX 580 and Radeon Instinct MI6
+  * GFX9 GPUs
+    * "Vega 10" chips, such as on the AMD Radeon RX Vega 64 and Radeon Instinct MI25
+    * "Vega 7nm" chips, such as on the Radeon Instinct MI50, Radeon Instinct MI60 or AMD Radeon VII
+
+ROCm is a collection of software ranging from drivers and runtimes to libraries and developer tools.
+Some of this software may work with more GPUs than the "officially supported" list above, though AMD does not make any official claims of support for these devices on the ROCm software platform.
+The following list of GPUs are enabled in the ROCm software, though full support is not guaranteed:
+
+  * GFX8 GPUs
+    * "Polaris 11" chips, such as on the AMD Radeon RX 570 and Radeon Pro WX 4100
+    * "Polaris 12" chips, such as on the AMD Radeon RX 550 and Radeon RX 540
+  * GFX7 GPUs
+    * "Hawaii" chips, such as the AMD Radeon R9 390X and FirePro W9100
+
+As described in the next section, GFX8 GPUs require PCI Express 3.0 (PCIe 3.0) with support for PCIe atomics. This requires both CPU and motherboard support. GFX9 GPUs require PCIe 3.0 with support for PCIe atomics by default, but they can operate in most cases without this capability.
+
+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.
+As such, they are not yet officially supported targets for ROCm.
+
+For a more detailed list of hardware support, please see [the following documentation](https://rocm.github.io/hardware.html).

 #### Supported CPUs
+As described above, GFX8 GPUs require PCIe 3.0 with PCIe atomics in order to run ROCm.
+In particular, the CPU and every active PCIe point between the CPU and GPU require support for PCIe 3.0 and PCIe atomics.
+The CPU root must indicate PCIe AtomicOp Completion capabilities and any intermediate switch must indicate PCIe AtomicOp Routing capabilities.

+Current CPUs which support PCIe Gen3 + PCIe Atomics are:

-Starting with ROCm 1.8 we have relexed the use PCIe Atomics and also PCIe Lane choice for Vega10/GFX9 class GPU.  So now you can support CPU with out PCIe Atomics and also use Gen2 x1 lanes. 
+  * AMD Ryzen CPUs
+  * The CPUs in AMD Ryzen APUs
+  * AMD Ryzen Threadripper CPUs
+  * AMD EPYC CPUs
+  * Intel Xeon E7 v3 or newer CPUs
+  * Intel Xeon E5 v3 or newer CPUs
+  * Intel Xeon E3 v3 or newer CPUs
+  * Intel Core i7 v4, Core i5 v4, Core i3 v4 or newer CPUs (i.e. Haswell family or newer)
+  * Some Ivy Bridge-E systems

-Currently our GFX8 GPU's (Fiji & Polaris Family)still need to use PCIe Gen 3 and PCIe Atomics, but are looking at relaxing this in a future release, once we have fully tested firmware. 
+Beginning with ROCm 1.8, GFX9 GPUs (such as Vega 10) no longer require PCIe atomics.
+We have similarly opened up more options for number of PCIe lanes.
+GFX9 GPUs can now be run on CPUs without PCIe atomics and on older PCIe generations, such as PCIe 2.0.
+This is not supported on GPUs below GFX9, e.g. GFX8 cards in the Fiji and Polaris families.

+If you are using any PCIe switches in your system, please note that PCIe Atomics are only supported on some switches, such as Broadcom PLX.
+When you install your GPUs, make sure you install them in a PCIe 3.1.0 x16, x8, x4, or x1 slot attached either directly to the CPU's Root I/O controller or via a PCIe switch directly attached to the CPU's Root I/O controller.

-Current CPUs which support PCIe Gen3 + PCIe Atomics are: 
-  * AMD Ryzen CPUs;
-  * AMD EPYC CPUs;  
-  * Intel Xeon E7 V3  or newer CPUs;
-  * Intel Xeon E5 v3 or newer CPUs; 
-  * Intel Xeon E3 v3 or newer CPUs; 
-  * Intel Core i7 v4, Core i5 v4, Core i3 v4 or newer CPUs (i.e. Haswell family or newer).
+In our experience, many issues stem from trying to use consumer motherboards which provide physical x16 connectors that are electrically connected as e.g. PCIe 2.0 x4, PCIe slots connected via the Southbridge PCIe I/O controller, or PCIe slots connected through a PCIe switch that does
+not support PCIe atomics.

-For FIJI and Polaris GPU's the ROCm Platform leverages PCIe Atomics (Fetch ADD, Compare and SWAP, 
-Unconditional SWAP, AtomicsOpCompletion).
-[PCIe atomics](https://github.com/RadeonOpenCompute/RadeonOpenCompute.github.io/blob/master/ROCmPCIeFeatures.md)
-PCIe Atomics are only supported on PCIe Gen3 Enabled CPUs and PCIe Gen3 Switches like
-Broadcom PLX. When you install your GPUs make sure you install them in a fully
-PCIe Gen3 x16 or x8, x4 or x1  slot attached either directly to the CPU's Root I/O 
-controller or via a PCIe switch directly attached to the CPU's Root I/O 
-controller. In our experience many issues stem from trying to use consumer 
-motherboards which provide Physical x16 Connectors that are electrically 
-connected as e.g. PCIe Gen2 x4 connected via the 
-Southbridge PCIe I/O controller. 
- 
-
-Experimental support for our GFX7 GPUs Radeon R9 290, R9 390, AMD FirePro S9150, S9170 note they do not support or
-take advantage of PCIe Atomics. However, we still recommend that you use a CPU
-from the list provided above. 
-
-#### Not supported or very limited support under ROCm 
-###### Limited Support 
-
-
-* With ROCm 1.8 and Vega10 it should support  PCIe Gen 2 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. But we have done very limited testing. Since our test farm today has been catering to CPU listed above.  This is where we need comunity support. 
- * Thunderbolt 1,2 &. 3 enabled breakout boxes GPU's should now be able to work with ROCm. Thunderbolt 1 & 2 are PCIe Gen2 based. But we have done no testing on this config and would need comunity support do limited access to this type of equipment 
-
-###### Not Supported 
-
-
-* We also do not support AMD Carrizo and Kaveri APU as host for compliant dGPU attachments.
- * Thunderbolt 1 and 2 enabled GPU's are not supported by ROCm. Thunderbolt 1 & 2 are PCIe Gen2 based.
- * AMD Carrizo based APUs have limited support due to OEM & ODM's choices when it comes to some key configuration parameters. On point, we have observed that Carrizo Laptops, AIOs and Desktop systems showed inconsistencies in exposing and enabling the System BIOS parameters required by the ROCm stack. Before purchasing a Carrizo system for ROCm, please verify that the BIOS provides an option for enabling IOMMUv2. If this is the case, the final requirement is associated with correct CRAT table support - please inquire with the OEM about the latter.
- * AMD Merlin/Falcon Embedded System is also not currently supported by the public Repo.
- * AMD Raven Ridge APU are currently not supported
-
-
-### New Features to ROCm 1.8
-
-#### DKMS driver installation
-
- * Debian packages are provided for DKMS on Ubuntu
- * RPM packages are provided for CentOS/RHEL 7.4 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 Distrubtuion Suppport 
-
- * Binary Package support for Ubuntu 16.04
- * Binary Package support for CentoOS 7.4
- * Binary Package support for RHEL 7.4
- 
-#### Improved OpenMPI via UCX support 
-
- * UCX support for OpenMPI
- * ROCm RDMA
-
-### The latest ROCm platform - ROCm 1.8
-
-The latest tested version of the drivers, tools, libraries and source code for
-the ROCm platform have been released and are available under the roc-1.8.x or rocm-1.8.x tag
-of the following GitHub repositories:
-
-* [ROCK-Kernel-Driver](https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/tree/roc-1.8.x)
-* [ROCR-Runtime](https://github.com/RadeonOpenCompute/ROCR-Runtime/tree/roc-1.8.x)
-* [ROCT-Thunk-Interface](https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface/tree/roc-1.8.x)
-* [ROC-smi](https://github.com/RadeonOpenCompute/ROC-smi/tree/roc-1.8.x)
-* [HCC compiler](https://github.com/RadeonOpenCompute/hcc/tree/roc-1.8.x)
-* [compiler-runtime](https://github.com/RadeonOpenCompute/compiler-rt/tree/roc-1.8.x)
-* [HIP](https://github.com/GPUOpen-ProfessionalCompute-Tools/HIP/tree/roc-1.8.x)
-* [HIP-Examples](https://github.com/GPUOpen-ProfessionalCompute-Tools/HIP-Examples/tree/roc-1.8.x)
-* [atmi](https://github.com/RadeonOpenCompute/atmi/tree/0.3.7)
-
-Additionally, the following mirror repositories that support the HCC compiler
-are also available on GitHub, and frozen for the rocm-1.8.0 release:
-
-* [llvm](https://github.com/RadeonOpenCompute/llvm/tree/roc-1.8.x)
-* [ldd](https://github.com/RadeonOpenCompute/lld/tree/roc-1.8.x)
-* [hcc-clang-upgrade](https://github.com/RadeonOpenCompute/hcc-clang-upgrade/tree/roc-1.8.x)
-* [ROCm-Device-Libs](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/roc-1.8.x)
-
-#### Supported Operating Systems - New operating systems available
-
-The ROCm 1.8 platform has been tested on the following operating systems:
- * Ubuntu 16.04
- * CentOS 7.4 (Using devetoolset-7 runtime support)
- * RHEL 7.4 (Using devetoolset-7 runtime support)
-
-### Installing from AMD ROCm repositories
-
-AMD is hosting both debian and RPM repositories for the ROCm 1.8 packages at this time.
-
-The packages in the Debian repository have been signed to ensure package integrity.
-
-#### Installing from a debian repository
-
-##### First make sure your system is up to date 
-
-```shell
-sudo apt update
-sudo apt dist-upgrade
-sudo apt install libnuma-dev
-sudo reboot
+If you attempt to run ROCm on a system without proper PCIe atomic support, you may see an error in the kernel log (`dmesg`):
 ```
-##### Optional: Upgrade to 4.13 kernel
-
-Although not required, it is recommended as of ROCm 1.8.0 that the system's kernel is upgraded to the latest 4.13 version available:
-
-```shell
-sudo apt install linux-headers-4.13.0-32-generic linux-image-4.13.0-32-generic linux-image-extra-4.13.0-32-generic linux-signed-image-4.13.0-32-generic
-sudo reboot 
-```
-##### Add the ROCm apt repository
-
-For Debian based systems, like Ubuntu, configure the Debian ROCm repository as
-follows:
-
-```shell
-wget -qO - http://repo.radeon.com/rocm/apt/debian/rocm.gpg.key | sudo apt-key add -
-sudo sh -c 'echo deb [arch=amd64] http://repo.radeon.com/rocm/apt/debian/ xenial main > /etc/apt/sources.list.d/rocm.list'
-```
-The gpg key might change, so it may need to be updated when installing a new 
-release. The current rocm.gpg.key is not avialable in a standard key ring distribution,
-but has the following sha1sum hash:
-
-f0d739836a9094004b0a39058d046349aacc1178  rocm.gpg.key
-
-##### Install
-
-Next, update the apt repository list and install the rocm package:
-
->**Warning**: Before proceeding, make sure to completely
->[uninstall any previous ROCm package](https://github.com/RadeonOpenCompute/ROCm#removing-pre-release-packages):
-
-```shell
-sudo apt update
-sudo apt install rocm-dkms
+kfd: skipped device 1002:7300, PCI rejects atomics
 ```

-###### Next set your permsions 
+Experimental support for our Hawaii (GFX7) GPUs (Radeon R9 290, R9 390, FirePro W9100, S9150, S9170)
+does not require or take advantage of PCIe Atomics. However, we still recommend that you use a CPU
+from the list provided above for compatibility purposes.

-With move to upstreaming the KFD driver and the support of DKMS,  for all Console aka headless user, you will need to add all  your users to the  'video" group by setting the Unix permissions
+#### Not supported or limited support under ROCm
+##### Limited support

-Configure 
-Ensure that your user account is a member of the "video" group prior to using the ROCm driver. You can find which groups you are a member of with the following command:
+* 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_.
+* 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.
+  * As of ROCm 2.1, "Carrizo" and "Bristol Ridge" require the use of upstream kernel drivers.
+  * In addition, various "Carrizo" and "Bristol Ridge" platforms may not work due to OEM and ODM choices when it comes to key configurations parameters such as inclusion of the required CRAT tables and IOMMU configuration parameters in the system BIOS.
+  * Before purchasing such a system for ROCm, please verify that the BIOS provides an option for enabling IOMMUv2 and that the system BIOS properly exposes the correct CRAT table. Inquire with your vendor about the latter.
+* AMD "Raven Ridge" APUs are enabled to run OpenCL, but do not yet support HCC, HIP, or our libraries built on top of these compilers and runtimes.
+  * As of ROCm 2.1, "Raven Ridge" requires the use of upstream kernel drivers.
+  * In addition, various "Raven Ridge" platforms may not work due to OEM and ODM choices when it comes to key configurations parameters such as inclusion of the required CRAT tables and IOMMU configuration parameters in the system BIOS.
+  * Before purchasing such a system for ROCm, please verify that the BIOS provides an option for enabling IOMMUv2 and that the system BIOS properly exposes the correct CRAT table. Inquire with your vendor about the latter.

-```shell
-groups
+##### Not supported
+
+* "Tonga", "Iceland", "Vega M", and "Vega 12" GPUs are not supported in ROCm 2.9.x
+* We do not support GFX8-class GPUs (Fiji, Polaris, etc.) on CPUs that do not have PCIe 3.0 with PCIe atomics.
+  * As such, we do not support AMD Carrizo and Kaveri APUs as hosts for such GPUs.
+  * Thunderbolt 1 and 2 enabled GPUs are not supported by GFX8 GPUs on ROCm. Thunderbolt 1 & 2 are based on PCIe 2.0.
+
+#### ROCm support in upstream Linux kernels
+
+As of ROCm 1.9.0, the ROCm user-level software is compatible with the AMD drivers in certain upstream Linux kernels.
+As such, users have the option of either using the ROCK kernel driver that are part of AMD's ROCm repositories or using the upstream driver and only installing ROCm user-level utilities from AMD's ROCm repositories.
+
+These releases of the upstream Linux kernel support the following GPUs in ROCm:
+ * 4.17: Fiji, Polaris 10, Polaris 11
+ * 4.18: Fiji, Polaris 10, Polaris 11, Vega10
+ * 4.20: Fiji, Polaris 10, Polaris 11, Vega10, Vega 7nm
+
+The upstream driver may be useful for running ROCm software on systems that are not compatible with the kernel driver available in AMD's repositories.
+For users that have the option of using either AMD's or the upstreamed driver, there are various tradeoffs to take into consideration:
+
+|   | Using AMD's `rock-dkms` package | Using the upstream kernel driver |
+| ---- | ------------------------------------------------------------| ----- |
+| Pros | More GPU features, and they are enabled earlier | Includes the latest Linux kernel features |
+|      | Tested by AMD on supported distributions | May work on other distributions and with custom kernels |
+|      | Supported GPUs enabled regardless of kernel version | |
+|      | Includes the latest GPU firmware | |
+| Cons | May not work on all Linux distributions or versions | Features and hardware support varies depending on kernel version |
+|      | Not currently supported on kernels newer than 5.4 | Limits GPU's usage of system memory to 3/8 of system memory (before 5.6). For 5.6 and beyond, both DKMS and upstream kernels allow use of 15/16 of system memory. |
+|      |   | IPC and RDMA capabilities are not yet enabled |
+|      |   | Not tested by AMD to the same level as `rock-dkms` package |
+|      |   | Does not include most up-to-date firmware |
+
+
+## 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:
+
+• 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
+
+The releases of the upstream Linux kernel support the following GPUs in ROCm:
+
+• Fiji, Polaris 10, Polaris 11
+• Fiji, Polaris 10, Polaris 11, Vega10
+• Fiji, Polaris 10, Polaris 11, Vega10, Vega 7nm
+
+
+
+## Machine Learning and High Performance Computing Software Stack for AMD GPU
+
+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
 ```

-To add yourself to the video group you will need the sudo password and can use the following command:
-
-```shell
-sudo usermod -a -G video $LOGNAME 
-``` 
-
-Once complete, reboot your system.
-
-Upon Reboot run 
-```shell
-rocminfo 
-clinfo 
-``` 
-
-If you have an [Install Issue ](https://rocm.github.io/install_issues.html) please read this FAQ .
-
- 
-###### Upon restart, To test your OpenCL instance 
-
- Build and run Hello World OCL app..
-
-HelloWorld sample:
-
-```shell
- wget https://raw.githubusercontent.com/bgaster/opencl-book-samples/master/src/Chapter_2/HelloWorld/HelloWorld.cpp
- wget https://raw.githubusercontent.com/bgaster/opencl-book-samples/master/src/Chapter_2/HelloWorld/HelloWorld.cl
-```
-
- Build it using the default ROCm OpenCL include and library locations:
-
-```shell
-g++ -I /opt/rocm/opencl/include/ ./HelloWorld.cpp -o HelloWorld -L/opt/rocm/opencl/lib/x86_64 -lOpenCL
-```
-
- Run it:
-
- ```shell
- ./HelloWorld
-```
-
-##### How to un-install from Ubuntu 16.04
-
-To un-install the entire rocm development package execute:
-
-```shell
-sudo apt autoremove rocm-dkms
-```
-
-##### Installing development packages for cross compilation
-
-It is often useful to develop and test on different systems. In this scenario,
-you may prefer to avoid installing the ROCm Kernel to your development system.
-
-In this case, install the development subset of packages:
-
-```shell
-sudo apt update
-sudo apt install rocm-dev
-```
-
->**Note:** To execute ROCm enabled apps you will require a system with the full
->ROCm driver stack installed
-
-##### Removing pre-release packages
-
-If you installed any of the ROCm pre-release packages from github, they will
-need to be manually un-installed:
-
-```shell
-sudo apt purge libhsakmt
-sudo apt purge compute-firmware
-sudo apt purge $(dpkg -l | grep 'kfd\|rocm' | grep linux | grep -v libc | awk '{print $2}')
-```
-
-If possible, we would recommend starting with a fresh OS install.
-
-### CentOS/RHEL 7 Support
-
-Support for CentOS/RHEL 7 has been added in ROCm 1.8, but requires a special 
-runtime environment provided by the RHEL Software Collections and additional
-dkms support packages to properly install in run.
-
-#### Preparing RHEL 7 for installation
-
-RHEL is a subscription based operating system, and must enable several external
-repositories to enable installation of the devtoolset-7 environment and the DKMS
-support files. These steps are not required for CentOS.
-
-First, the subscription for RHEL must be enabled and attached to a pool id. Please
-see Obtaining an RHEL image and license page for instructions on registering your
-system with the RHEL subscription server and attaching to a pool id.
-
-
-Second, enable the following repositories:
-
-```shell
-sudo subscription-manager repos --enable rhel-7-server-rhscl-rpms
-sudo subscription-manager repos --enable rhel-7-server-optional-rpms
-sudo subscription-manager repos --enable rhel-7-server-extras-rpms
-```
-
-Third, enable additional repositories by downloading and installing the epel-release-latest-7 repository RPM:
-
-```shell
-sudo rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-```
-
-#### Install and setup Devtoolset-7
-
-To setup the Devtoolset-7 environment, follow the instructions on this page:
-
-https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
-
-Note that devtoolset-7 is a Software Collections package, and is not supported by AMD.
-
-#### Prepare CentOS/RHEL 7.4 for DKMS Install
-
-Installing kernel drivers on CentOS/RHEL 7.4 requires dkms tool being installed:
-
-```shell
-sudo yum install -y epel-release
-sudo yum install -y dkms kernel-headers-`uname -r`
-```
-
-
-At this point they system can install ROCm using the DKMS drivers.
-
-Installing ROCm on the system
-At this point ROCm can be installed on the target system. Create a /etc/yum.repos.d/rocm.repo file with the following contents:
-
-```shell
-[ROCm]
-name=ROCm
-baseurl=http://repo.radeon.com/rocm/yum/rpm
-enabled=1
-gpgcheck=0
-```
-
-The repo's URL should point to the location of the repositories repodata database. Install ROCm components using these commands:
-
-```shell
-sudo yum install rocm-dkms
-```
-
-The rock-dkms component should be installed and the /dev/kfd device should be available on reboot.
-
-Ensure that your user account is a member of the "video" or "wheel" group prior to using the ROCm driver.
-You can find which groups you are a member of with the following command:
-
-```shell
-groups
-```
-
-To add yourself to the video (or wheel) group you will need the sudo password and can use the
-following command:
-
-```shell
-sudo usermod -a -G video $LOGNAME 
-```
-
-Current release supports up to CentOS/RHEL 7.4. If for any reason the system needs to be updated to 7.5, don’t update the kernel. Add “--exclude=kernel*” flag to yum install. For example:
-
-```shell
-sudo yum update --exclude=kernel*
-```
-
-#### Compiling applications using hcc, hip, etc.
-
-To compile applications or samples, please use gcc-7.2 provided by the devtoolset-7 environment.
-To do this, compile all applications after running this command: 
-
-```shell
-scl enable devtoolset-7 bash
-```
-#### How to un-install ROCm from CentOS/RHEL 7.4
-
-To un-install the entire rocm development package execute:
-
-```shell
-sudo yum autoremove rocm-dkms
-```
-
-#### Known Issues / Workarounds
-
-##### If you Plan to Run with X11 - we are seeing  X freezes under load
-
-ROCm 1.8.0 a kernel parameter noretry has been set to 1 to improve overall system performance. However it has been proven to bring instability to graphics driver shipped with Ubuntu. This is an ongoing issue and we are looking into it.
-
-Before that, please try apply this change by changing noretry bit to 0.
-
-```shell
-echo 0 | sudo tee /sys/module/amdkfd/parameters/noretry
-```
-
-Files under /sys won't be preserved after reboot so you'll need to do it every time.
-
-One way to keep noretry=0 is to change /etc/modprobe.d/amdkfd.conf and make it be:
-
-options amdkfd noretry=0
-
-Once it's done, run sudo update-initramfs -u. Reboot and verify /sys/module/amdkfd/parameters/noretry stays as 0.
-
-##### If you are you are using hipCaffe Alexnet training on ImageNet - we are seeing sporadic hangs of hipCaffe during training
-
-#### Closed source components
-
-The ROCm platform relies on a few closed source components to provide legacy
-functionality like HSAIL finalization and debugging/profiling support. These
-components are only available through the ROCm repositories, and will either be
-deprecated or become open source components in the future. These components are
-made available in the following packages:
-
-*  hsa-ext-rocr-dev
-
-### Getting ROCm source code
-
-Modifications can be made to the ROCm 1.8 components by modifying the open
-source code base and rebuilding the components. Source code can be cloned from
-each of the GitHub repositories using git, or users can use the repo command
-and the ROCm 1.8 manifest file to download the entire ROCm 1.8 source code.
-
-#### Installing repo
-
-Google's repo tool allows you to manage multiple git repositories
-simultaneously. You can install it by executing the following commands:
-
-```shell
-curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
-chmod a+x ~/bin/repo
-```
-Note: make sure ~/bin exists and it is part of your PATH
-
-#### Cloning the code
-
-```shell
-mkdir ROCm && cd ROCm
-repo init -u https://github.com/RadeonOpenCompute/ROCm.git -b roc-1.8.0
-repo sync
-```
-These series of commands will pull all of the open source code associated with
-the ROCm 1.8 release. Please ensure that ssh-keys are configured for the
-target machine on GitHub for your GitHub ID.
-
-* OpenCL Runtime and Compiler will be submitted to the Khronos Group, prior to
-  the final release, for conformance testing.
+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)
--- a/default.xml
+++ b/default.xml
@@ -2,26 +2,84 @@
 <manifest>

    <remote name="roc-github"
-            fetch="ssh://git@github.com/RadeonOpenCompute/" />
-    <remote name="pctools-github"
-            fetch="ssh://git@github.com/GPUOpen-ProfessionalCompute-Tools/" />
+            fetch="http://github.com/RadeonOpenCompute/" />
+    <remote name="rocm-devtools"
+            fetch="https://github.com/ROCm-Developer-Tools/" />
+    <remote name="rocm-swplat"
+            fetch="https://github.com/ROCmSoftwarePlatform/" />
+    <remote name="gpuopen-libs"
+            fetch="https://github.com/GPUOpen-ProfessionalCompute-Libraries/" />
+    <remote name="gpuopen-tools"
+            fetch="https://github.com/GPUOpen-Tools/" />

-    <default revision="roc-1.7.x"
+    <default revision="refs/tags/rocm-3.3.0"
             remote="roc-github"
+             sync-c="true"
             sync-j="4" />

-    <project path="ROCK-Kernel-Driver" name="ROCK-Kernel-Driver" />
-    <project path="ROCT-Thunk-Interface" name="ROCT-Thunk-Interface" />
-    <project path="ROC-smi" name="ROC-smi" />
-    <project path="ROCR-Runtime" name="ROCR-Runtime" />
-    <project path="hcc" name="hcc" />
-    <project path="compiler-rt" name="compiler-rt" />
-    <project path="HIP" remote="pctools-github" name="HIP" />
-    <project path="HIP-Examples" remote="pctools-github" name="HIP-Examples" />
-    <project path="atmi" name="atmi" revision="master" />
-    <project path="llvm" name="llvm" />
-    <project path="lld" name="lld" />
-    <project path="hcc-clang-upgrade" name="hcc-clang-upgrade" />
-    <project path="ROCm-Device-Libs" name="ROCm-Device-Libs" />
+    <project name="ROCK-Kernel-Driver" revision="refs/tags/roc-3.3.0" />
+    <project name="ROCT-Thunk-Interface" revision="refs/tags/roc-3.3.0" />
+    <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="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 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" />
+    <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="ROCm-CompilerSupport" />
+    <project name="rocr_debug_agent" remote="rocm-devtools" revision="refs/tags/roc-3.3.0" />
+    <project name="rocm_bandwidth_test" />
+    <project name="RCP" remote="gpuopen-tools" revision="3a49405a1500067c49d181844ec90aea606055bb" />
+
+    <!-- ROCm Libraries -->
+    <project name="rocBLAS" remote="rocm-swplat" />
+    <project name="hipBLAS" remote="rocm-swplat" />
+    <project name="rocFFT" remote="rocm-swplat" revision="refs/tags/rocm-3.3" />
+    <project name="rocRAND" remote="rocm-swplat" />
+    <project name="rocSPARSE" 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="rccl" remote="rocm-swplat" />
+    <project name="MIVisionX" remote="gpuopen-libs" revision="refs/tags/1.7" />
+    <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" />
 </manifest>
--- a/onnx.png
+++ b/onnx.png
--- a/singleinstance.png
+++ b/singleinstance.png
--- a/version_history.md
+++ b/version_history.md
@@ -0,0 +1,503 @@
+## 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