Update README.md

ROCm release 3.3 Manifest File

README.md

@@ -1,110 +1,228 @@
+# 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.
 
-## Are You Ready to ROCK?
-The ROCm Platform brings a rich foundation to advanced computing by seamlessly integrating the CPU and GPU with the goal of solving real-world problems.
-This software enables the high-performance operation of AMD GPUs for computation oriented tasks in the Linux operating system.
-Please refer the ROCm Documentation [here](https://rocm-documentation.readthedocs.io/en/latest/index.html).
-
-### Current ROCm Version: 2.9
-
-- [New features and enhancements in ROCm 2.9](#new-features-and-enhancements-in-rocm-29)
-- [The latest ROCm platform - ROCm 2.9](#the-latest-rocm-platform-rocm-29)
-- [Hardware Support](#hardware-support)
-  * [Supported GPUs](#supported-gpus)
-  * [Supported CPUs](#supported-cpus)
-  * [Not supported or limited support under ROCm](#not-supported-or-limited-support-under-rocm)
-- [Supported Operating Systems](#supported-operating-systems-new-operating-systems-available)
-  * [ROCm support in upstream Linux kernels](#rocm-support-in-upstream-linux-kernels)
-- [Installing from AMD ROCm repositories](#installing-from-amd-rocm-repositories)
-  * [ROCm Binary Package Structure](#rocm-binary-package-structure)
-  * [Ubuntu Support - installing from a Debian repository](#ubuntu-support-installing-from-a-debian-repository)
-  * [CentOS/RHEL 7 (7.6) Support](#centosrhel-7-76-support)
-- [Known issues / workarounds](#known-issues-workarounds)
-- [Closed source components](#closed-source-components)
-- [Getting ROCm source code](#getting-rocm-source-code)
-  * [Installing repo](#installing-repo)
-  * [Downloading the ROCm source code](#downloading-the-rocm-source-code)
-  * [Building the ROCm source code](#building-the-rocm-source-code)
-- [Deprecation Notice](#deprecation-notice-hcc)
-- [Final notes](#final-notes)
+- [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)
 
 
-### New features and enhancements in ROCm 2.9
+- [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)
+  
 
-#### 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.
+## 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. 
 
-#### 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.
+Note: You can also clone the source code for individual ROCm components from the GitHub repositories.
 
 
-Features and enhancements introduced in previous versions of ROCm can be found in [version_history.md](version_history.md)
+### ROCm Components
+The following components for the ROCm platform are released and available for the v3.3
+release:
 
-### The latest ROCm platform - ROCm 2.9
+• Drivers
 
-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:
+• Tools
 
-* ROCm Core Components
-  - [ROCk Kernel Driver](https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/tree/roc-2.9.0)
-  - [ROCr Runtime](https://github.com/RadeonOpenCompute/ROCR-Runtime/tree/roc-2.9.0)
-  - [ROCt Thunk Interface](https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface/tree/roc-2.9.0)
-* ROCm Support Software
-  - [ROCm SMI](https://github.com/RadeonOpenCompute/ROC-smi/tree/roc-2.9.0)
-  - [ROCm cmake](https://github.com/RadeonOpenCompute/rocm-cmake/tree/roc-2.9.0)
-  - [rocminfo](https://github.com/RadeonOpenCompute/rocminfo/tree/roc-2.9.0)
-  - [ROCm Bandwidth Test](https://github.com/RadeonOpenCompute/rocm_bandwidth_test/tree/roc-2.9.0)
-* ROCm Development Tools
-  - [HCC compiler](https://github.com/RadeonOpenCompute/hcc/tree/roc-hcc-2.9.0)
-  - [HIP](https://github.com/ROCm-Developer-Tools/HIP/tree/roc-2.9.0)
-  - [ROCm Device Libraries](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/roc-hcc-2.9.0)
-  - ROCm OpenCL, which is created from the following components:
-    - [ROCm OpenCL Runtime](http://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime/tree/roc-2.9.0)
-    - [ROCm OpenCL Driver](http://github.com/RadeonOpenCompute/ROCm-OpenCL-Driver/tree/roc-2.9.0)
-  - The ROCm OpenCL compiler, which is created from the following components:
-      - [ROCm LLVM OCL](http://github.com/RadeonOpenCompute/llvm/tree/roc-ocl-2.9.0)
-      - [ROCm LLVM HCC](http://github.com/RadeonOpenCompute/llvm/tree/roc-hcc-2.9.0)
-      - [ROCm Clang](http://github.com/RadeonOpenCompute/clang/tree/roc-2.9.0)
-      - [ROCm lld OCL](http://github.com/RadeonOpenCompute/lld/tree/roc-ocl-2.9.0)
-      - [ROCm lld HCC](http://github.com/RadeonOpenCompute/lld/tree/roc-hcc-2.9.0)
-      - [ROCm Device Libraries](https://github.com/RadeonOpenCompute/ROCm-Device-Libs/tree/roc-2.9.x)
-  - [ROCM Clang-OCL Kernel Compiler](https://github.com/RadeonOpenCompute/clang-ocl/tree/roc-2.9.0)
-  - [Asynchronous Task and Memory Interface (ATMI)](https://github.com/RadeonOpenCompute/atmi/tree/rocm_2.9.0)
-  - [ROCr Debug Agent](https://github.com/ROCm-Developer-Tools/rocr_debug_agent/tree/roc-2.9.0)
-  - [ROCm Code Object Manager](https://github.com/RadeonOpenCompute/ROCm-CompilerSupport/tree/roc-2.9.0)
-  - [ROC Profiler](https://github.com/ROCm-Developer-Tools/rocprofiler/tree/roc-2.9.0)
-  - [ROC Tracer](https://github.com/ROCm-Developer-Tools/roctracer/tree/roc-2.9.x)
-  - [Radeon Compute Profiler](https://github.com/GPUOpen-Tools/RCP/tree/3a49405)
-  - Example Applications:
-    - [HCC Examples](https://github.com/ROCm-Developer-Tools/HCC-Example-Application/tree/ffd65333)
-    - [HIP Examples](https://github.com/ROCm-Developer-Tools/HIP-Examples/tree/roc-2.9.0)
-* ROCm Libraries
-  - [rocBLAS](https://github.com/ROCmSoftwarePlatform/rocBLAS/tree/rocm-2.9)
-  - [hipBLAS](https://github.com/ROCmSoftwarePlatform/hipBLAS/tree/rocm-2.9)
-  - [rocFFT](https://github.com/ROCmSoftwarePlatform/rocFFT/tree/rocm-2.9)
-  - [rocRAND](https://github.com/ROCmSoftwarePlatform/rocRAND/tree/2.9.0)
-  - [rocSPARSE](https://github.com/ROCmSoftwarePlatform/rocSPARSE/tree/rocm-2.9)
-  - [hipSPARSE](https://github.com/ROCmSoftwarePlatform/hipSPARSE/tree/rocm-2.9)
-  - [rocALUTION](https://github.com/ROCmSoftwarePlatform/rocALUTION/tree/rocm-2.9)
-  - [MIOpenGEMM](https://github.com/ROCmSoftwarePlatform/MIOpenGEMM/tree/6275a879)
-  - [MIOpen](https://github.com/ROCmSoftwarePlatform/MIOpen/tree/roc-2.9.0)
-  - [rocThrust](https://github.com/ROCmSoftwarePlatform/rocThrust/tree/2.9.0)
-  - [ROCm SMI Lib](https://github.com/RadeonOpenCompute/rocm_smi_lib/tree/roc-2.9.0)
-  - [RCCL](https://github.com/ROCmSoftwarePlatform/rccl/tree/2.9.0)
-  - [MIVisionX](https://github.com/GPUOpen-ProfessionalCompute-Libraries/MIVisionX/tree/1.3.0)
-  - [hipCUB](https://github.com/ROCmSoftwarePlatform/hipCUB/tree/2.9.0)
+• Libraries
 
-### Hardware Support
+• 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.
 
@@ -162,7 +280,7 @@ GFX9 GPUs can now be run on CPUs without PCIe atomics and on older PCIe generati
 This is not supported on GPUs below GFX9, e.g. GFX8 cards in the Fiji and Polaris families.
 
 If you are using any PCIe switches in your system, please note that PCIe Atomics are only supported on some switches, such as Broadcom PLX.
-When you install your GPUs, make sure you install them in a PCIe 3.0 x16, x8, x4, or x1 slot attached either directly to the CPU's Root I/O controller or via a PCIe switch directly attached to the CPU's Root I/O controller.
+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.
 
 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.
@@ -180,7 +298,7 @@ from the list provided above for compatibility purposes.
 ##### Limited support
 
 * ROCm 2.9.x should support PCIe 2.0 enabled CPUs such as the AMD Opteron, Phenom, Phenom II, Athlon, Athlon X2, Athlon II and older Intel Xeon and Intel Core Architecture and Pentium CPUs. However, we have done very limited testing on these configurations, since our test farm has been catering to CPUs listed above. This is where we need community support. _If you find problems on such setups, please report these issues_.
-* Thunderbolt 1, 2, and 3 enabled breakout boxes should now be able to work with ROCm. Thunderbolt 1 and 2 are PCIe 2.0 based, and thus are only supported with GPUs that do not require PCIe 3.0 atomics (e.g. Vega 10). However, we have done no testing on this configuration and would need community support due to limited access to this type of equipment.
+* 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.
@@ -197,14 +315,6 @@ from the list provided above for compatibility purposes.
   * As such, we do not support AMD Carrizo and Kaveri APUs as hosts for such GPUs.
   * Thunderbolt 1 and 2 enabled GPUs are not supported by GFX8 GPUs on ROCm. Thunderbolt 1 & 2 are based on PCIe 2.0.
 
-### Supported Operating Systems - New operating systems available
-
-The ROCm 2.9.x platform supports the following operating systems:
-
- * Ubuntu 16.04.5(Kernel 4.15) and 18.04.3(Kernel 4.15 and Kernel 4.18)
- * CentOS 7.6 (Using devtoolset-7 runtime support)
- * RHEL 7.6 (Using devtoolset-7 runtime support)
-
 #### ROCm support in upstream Linux kernels
 
 As of ROCm 1.9.0, the ROCm user-level software is compatible with the AMD drivers in certain upstream Linux kernels.
@@ -225,21 +335,34 @@ For users that have the option of using either AMD's or the upstreamed driver, t
 |      | Supported GPUs enabled regardless of kernel version | |
 |      | Includes the latest GPU firmware | |
 | Cons | May not work on all Linux distributions or versions | Features and hardware support varies depending on kernel version |
-|      | Not currently supported on kernels newer than 4.18 | Limits GPU's usage of system memory to 3/8 of system memory |
+|      | 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 |
 
 
-### Installing from AMD ROCm repositories
+## 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:
 
-AMD hosts both [Debian](http://repo.radeon.com/rocm/apt/debian/) and [RPM](http://repo.radeon.com/rocm/yum/rpm/) repositories for the ROCm 2.9.x packages at this time.
+• 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 packages in the Debian repository have been signed to ensure package integrity.
+The releases of the upstream Linux kernel support the following GPUs in ROCm:
 
-#### ROCm Binary Package Structure
+• Fiji, Polaris 10, Polaris 11
+• Fiji, Polaris 10, Polaris 11, Vega10
+• Fiji, Polaris 10, Polaris 11, Vega10, Vega 7nm
 
-ROCm is a collection of software ranging from drivers and runtimes to libraries and developer tools.
+
+
+## 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.
@@ -296,411 +419,133 @@ The chain of software installed by these meta-packages is illustrated below
   rocm-dkms
     |--rock-dkms
     \--rocm-dev
-       |--hsa-rocr-dev
-       |--hsa-ext-rocr-dev
-       |--hsakmt-roct
-       |--hsakmt-roct-dev
-       |--rocm-cmake
-       |--rocm-device-libs
+       |--comgr
        |--hcc
        |--hip_base
        |--hip_doc
        |--hip_hcc
        |--hip_samples
-       |--rocm-smi
+       |--hsakmt-roct
+       |--hsakmt-roct-dev
        |--hsa-amd-aqlprofile
-       |--comgr
+       |--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
-    |--rocalution
     |--hipblas
+    |--hipcub
+    |--hipsparse
+    |--rocalution
     |--rocblas
     |--rocfft
+    |--rocprim
     |--rocrand
-    |--hipsparse
-    \--rocsparse
+    |--rocsparse
+    \--rocthrust
 ```
 
 These meta-packages are not required but may be useful to make it easier to install ROCm on most systems.
-Some users may want to skip certain packages. For instance, a user that wants to use the upstream kernel drivers (rather than those supplied by AMD) may want to skip the `rocm-dkms` and `rock-dkms` packages, and instead directly install `rocm-dev`.
 
-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.
-
-#### Ubuntu Support - installing from a Debian repository
-
-The following directions show how to install ROCm on supported Debian-based systems such as Ubuntu 18.04.
-These directions may not work as written on unsupported Debian-based distributions.
-For example, newer versions of Ubuntu may not be compatible with the `rock-dkms` kernel driver.
-As such, users may want to skip the `rocm-dkms` and `rock-dkms` packages, as described [above](#rocm-binary-package-structure), and instead [use the upstream kernel driver](#using-debian-based-rocm-with-upstream-kernel-drivers).
-
-##### First make sure your system is up to date
-
-```shell
-sudo apt update
-sudo apt dist-upgrade
-sudo apt install libnuma-dev
-sudo reboot
-```
-
-##### Add the ROCm apt repository
-
-For Debian-based systems like Ubuntu, configure the Debian ROCm repository as
-follows:
-
-```shell
-wget -qO - http://repo.radeon.com/rocm/apt/debian/rocm.gpg.key | sudo apt-key add -
-echo 'deb [arch=amd64] http://repo.radeon.com/rocm/apt/debian/ xenial main' | sudo tee /etc/apt/sources.list.d/rocm.list
-```
-The gpg key might change, so it may need to be updated when installing a new release.
-If the key signature verification is failed while update, please re-add the key from
-ROCm apt repository. The current rocm.gpg.key is not available in a standard key ring
-distribution, but has the following sha1sum hash:
-
-`e85a40d1a43453fe37d63aa6899bc96e08f2817a  rocm.gpg.key`
-
-##### Install
-
-Next, update the apt repository list and install the `rocm-dkms` meta-package:
-
-```shell
-sudo apt update
-sudo apt install rocm-dkms
-```
-
-##### Next set your permissions
-
-Users will need to be in the `video` group in order to have access to the GPU.
-As such, you should ensure that your user account is a member of the `video` group prior to using ROCm.
-You can find which groups you are a member of with the following command:
-
-```shell
-groups
-```
-
-To add yourself to the video group you will need the sudo password and can use the following command:
-
-```shell
-sudo usermod -a -G video $LOGNAME
-```
-
-You may want to ensure that any future users you add to your system are put into the "video" group by default. To do that, you can run the following commands:
-
-```shell
-echo 'ADD_EXTRA_GROUPS=1' | sudo tee -a /etc/adduser.conf
-echo 'EXTRA_GROUPS=video' | sudo tee -a /etc/adduser.conf
-```
-
-Once complete, reboot your system.
-
-##### Test basic ROCm installation
-
-After rebooting the system run the following commands to verify that the ROCm installation was successful. If you see your GPUs listed by both of these commands, you should be ready to go!
-
-```shell
-/opt/rocm/bin/rocminfo
-/opt/rocm/opencl/bin/x86_64/clinfo
-```
-
-Note that, to make running ROCm programs easier, you may wish to put the ROCm binaries in your PATH.
-
-```shell
-echo 'export PATH=$PATH:/opt/rocm/bin:/opt/rocm/profiler/bin:/opt/rocm/opencl/bin/x86_64' | sudo tee -a /etc/profile.d/rocm.sh
-```
-
-If you have an [install issue](https://rocm.github.io/install_issues.html) please read this FAQ.
-
-##### Performing an OpenCL-only Installation of ROCm
-
-Some users may want to install a subset of the full ROCm installation.
-In particular, if you are trying to install on a system with a limited amount of storage space, or which will only run a small collection of known applications, you may want to install only the packages that are required to run OpenCL applications.
-To do that, you can run the following installation command **instead** of the command to install `rocm-dkms`.
-
-```shell
-sudo apt-get install dkms rock-dkms rocm-opencl-dev
-```
-
-##### How to uninstall from Ubuntu 16.04 or Ubuntu 18.04
-
-To uninstall the ROCm packages installed in the above directions, you can execute;
-
-```shell
-sudo apt autoremove rocm-dkms rocm-dev rocm-utils
-```
-
-##### Installing development packages for cross compilation
-
-It is often useful to develop and test on different systems.
-For example, some development or build systems may not have an AMD GPU installed.
-In this scenario, you may prefer to avoid installing the ROCK kernel driver to your development system.
-
-In this case, install the development subset of packages:
-
-```shell
-sudo apt update
-sudo apt install rocm-dev
-```
->**Note:** To execute ROCm enabled apps you will require a system with the full
->ROCm driver stack installed
-
-##### Using Debian-based ROCm with upstream kernel drivers
-
-As described in [the above section about upstream Linux kernel support](#rocm-support-in-upstream-linux-kernels), users may want to try installing ROCm user-level software without installing AMD's custom ROCK kernel driver.
-Users who do want to use upstream kernels can run the following commands instead of installing `rocm-dkms`
-
-```shell
-sudo apt update
-sudo apt install rocm-dev
-echo 'SUBSYSTEM=="kfd", KERNEL=="kfd", TAG+="uaccess", GROUP="video"' | sudo tee /etc/udev/rules.d/70-kfd.rules
-```
-
-#### CentOS/RHEL 7 (7.6) Support
-
-The following directions show how to install ROCm on supported RPM-based systems such as CentOS 7.6.
-These directions may not work as written on unsupported RPM-based distributions.
-For example, Fedora may work but may not be compatible with the `rock-dkms` kernel driver.
-As such, users may want to skip the `rocm-dkms` and `rock-dkms` packages, as described [above](#rocm-binary-package-structure), and instead [use the upstream kernel driver](#using-rpm-based-rocm-with-upstream-kernel-drivers).
-
-Support for CentOS/RHEL 7 was added in ROCm 1.8, but ROCm requires a special
-runtime environment provided by the RHEL Software Collections and additional
-dkms support packages to properly install and run.
-
-##### Preparing RHEL 7 (7.6) for installation
-
-RHEL is a subscription-based operating system, and you must enable several external
-repositories to enable installation of the devtoolset-7 environment and the DKMS
-support files. These steps are not required for CentOS.
-
-First, the subscription for RHEL must be enabled and attached to a pool id. Please
-see Obtaining an RHEL image and license page for instructions on registering your
-system with the RHEL subscription server and attaching to a pool id.
-
-
-Second, enable the following repositories:
-
-```shell
-sudo subscription-manager repos --enable rhel-server-rhscl-7-rpms
-sudo subscription-manager repos --enable rhel-7-server-optional-rpms
-sudo subscription-manager repos --enable rhel-7-server-extras-rpms
-```
-
-Third, enable additional repositories by downloading and installing the epel-release-latest-7 repository RPM:
-
-```shell
-sudo rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-```
-
-##### Install and setup Devtoolset-7
-
-To setup the Devtoolset-7 environment, follow the instructions on this page:
-
-https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
-
-Note that devtoolset-7 is a Software Collections package, and it is not supported by AMD.
-
-##### Prepare CentOS/RHEL (7.6) for DKMS Install
-
-Installing kernel drivers on CentOS/RHEL 7.6 requires dkms tool being installed:
-
-```shell
-sudo yum install -y epel-release
-sudo yum install -y dkms kernel-headers-`uname -r` kernel-devel-`uname -r`
-```
-
-##### Installing ROCm on the system
-
-It is recommended to [remove previous ROCm installations](https://github.com/RadeonOpenCompute/ROCm#how-to-uninstall-rocm-from-centosrhel-76) before installing the latest version to ensure a smooth installation.
-
-At this point ROCm can be installed on the target system. Create a /etc/yum.repos.d/rocm.repo file with the following contents:
-
-```shell
-[ROCm]
-name=ROCm
-baseurl=http://repo.radeon.com/rocm/yum/rpm
-enabled=1
-gpgcheck=0
-```
-
-The repo's URL should point to the location of the repositories repodata database. Install ROCm components using these commands:
-
-```shell
-sudo yum install rocm-dkms
-```
-
-The rock-dkms component should be installed and the `/dev/kfd` device should be available on reboot.
-
-##### Set up permissions
-
-Ensure that your user account is a member of the "video" or "wheel" group prior to using the ROCm driver.
-You can find which groups you are a member of with the following command:
-
-```shell
-groups
-```
-
-To add yourself to the video (or wheel) group you will need the sudo password and can use the
-following command:
-
-```shell
-sudo usermod -a -G video $LOGNAME
-```
-
-You may want to ensure that any future users you add to your system are put into the "video" group by default. To do that, you can run the following commands:
-
-```shell
-echo 'ADD_EXTRA_GROUPS=1' | sudo tee -a /etc/adduser.conf
-echo 'EXTRA_GROUPS=video' | sudo tee -a /etc/adduser.conf
-```
-
-Current release supports CentOS/RHEL 7.6. If users want to update the OS version, they should completely remove ROCm packages before updating to the latest version of the OS, to avoid DKMS related issues.
-
-Once complete, reboot your system.
-
-###### Test basic ROCm installation
-
-After rebooting the system run the following commands to verify that the ROCm installation was successful. If you see your GPUs listed by both of these commands, you should be ready to go!
-
-```shell
-/opt/rocm/bin/rocminfo
-/opt/rocm/opencl/bin/x86_64/clinfo
-```
-
-Note that, to make running ROCm programs easier, you may wish to put the ROCm binaries in your PATH.
-
-```shell
-echo 'export PATH=$PATH:/opt/rocm/bin:/opt/rocm/profiler/bin:/opt/rocm/opencl/bin/x86_64' | sudo tee -a /etc/profile.d/rocm.sh
-```
-
-If you have an [install issue](https://rocm.github.io/install_issues.html) please read this FAQ.
-
-###### Performing an OpenCL-only Installation of ROCm
-
-Some users may want to install a subset of the full ROCm installation.
-In particular, if you are trying to install on a system with a limited amount of storage space, or which will only run a small collection of known applications, you may want to install only the packages that are required to run OpenCL applications.
-To do that, you can run the following installation command **instead** of the command to install `rocm-dkms`.
-
-```shell
-sudo yum install rock-dkms rocm-opencl-devel
-```
-
-##### Compiling applications using HCC, HIP, and other ROCm software
-
-To compile applications or samples, please use gcc-7.2 provided by the devtoolset-7 environment.
-To do this, compile all applications after running this command:
-
-```shell
-scl enable devtoolset-7 bash
-```
-##### How to uninstall ROCm from CentOS/RHEL 7.6
-
-To uninstall the ROCm packages installed by the above directions, you can execute:
-
-```shell
-sudo yum autoremove rocm-dkms rock-dkms
-```
-
-##### Installing development packages for cross compilation
-
-It is often useful to develop and test on different systems.
-For example, some development or build systems may not have an AMD GPU installed.
-In this scenario, you may prefer to avoid installing the ROCK kernel driver to your development system.
-
-In this case, install the development subset of packages:
-
-```shell
-sudo yum install rocm-dev
-```
->**Note:** To execute ROCm enabled apps you will require a system with the full
->ROCm driver stack installed
-
-##### Using ROCm with upstream kernel drivers
-
-As described in [the above section about upstream Linux kernel support](#rocm-support-in-upstream-linux-kernels), use
-rs may want to try installing ROCm user-level software without installing AMD's custom ROCK kernel driver.
-Users who do want to use upstream kernels can run the following commands instead of installing `rocm-dkms`
-
-```shell
-sudo yum install rocm-dev
-echo 'SUBSYSTEM=="kfd", KERNEL=="kfd", TAG+="uaccess", GROUP="video"' | sudo tee /etc/udev/rules.d/70-kfd.rules
-```
-
-### Known issues / workarounds
-
-#### Docker container environment variable setting
-Applications fail when docker container is launched on NUMA system without --security-opt seccomp=unconfined. Please set "--security-opt seccomp=unconfined" to avoid this issue.
-
-### Closed source components
-
-The ROCm platform relies on a few closed source components to provide functionality
-such as HSA image support. These components are only available through the ROCm
-repositories, and they will either be deprecated or become open source components in the
-future. These components are made available in the following packages:
-
-*  hsa-ext-rocr-dev
-
-### Getting ROCm source code
-
-ROCm is built from open source software.
-As such, it is possible to make modifications to the various components of ROCm by downloading the source code, making modifications to it, and rebuilding the components.
-The source code for ROCm components can be cloned from each of the GitHub repositories using git.
-In order to make it easier to download the correct versions of each of these tools, this ROCm repository contains a [repo](https://gerrit.googlesource.com/git-repo/) manifest file, [default.xml](default.xml).
-Interested users can thus use this manifest file to download the source code for all of the ROCm software.
-
-#### Installing repo
-
-Google's repo tool allows you to manage multiple git repositories simultaneously.
-You can install it by executing the following example commands:
-
-```shell
-mkdir -p ~/bin/
-curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
-chmod a+x ~/bin/repo
-```
-Note that you can choose a different folder to install repo into if you desire. `~/bin/` is simply used as an example.
-
-#### Downloading the ROCm source code
-
-The following example shows how to use the `repo` binary downloaded above to download all of the ROCm source code.
-If you chose a directory other than `~/bin/` to install `repo`, you should use that directory below.
-
-```shell
-mkdir -p ~/ROCm/
-cd ~/ROCm/
-~/bin/repo init -u https://github.com/RadeonOpenCompute/ROCm.git -b roc-2.9.0
-repo sync
-```
-
-This will cause repo to download all of the open source code associated with this ROCm release.
-You may want to ensure that you have ssh-keys configured on your machine for your GitHub ID.
-
-#### Building the ROCm source code
-
-Each ROCm component repository contains directions for building that component.
-As such, you should go to the repository you are interested in building to find how to build it.
-
-That said, AMD also offers [a project](https://github.com/RadeonOpenCompute/Experimental_ROC) that demonstrates how to download, build, package, and install ROCm software on various distributions.
-The scripts here may be useful for anyone looking to build ROCm components.
-
-#### Deprecation Notice
-
-### HCC
-AMD is deprecating HCC to put more focus on HIP development and on
-other languages supporting heterogeneous compute.  We will no longer
-develop any new feature in HCC. We will stop maintaining HCC after
-its final release, which is planned for the end of 2019.  If your
-application was developed with the hc C++ API, we would encourage you
-to transition it to other languages supported by AMD, such as HIP or
-OpenCL.  HIP and hc languages share the same compiler technology, so
-many hc kernel language features (including inline assembly) are also
-available through the HIP compilation path.
-
-### hipThrust
-hip-thrust has been removed in ROCm2.7.
-
-
-### Final notes
-* OpenCL Runtime and Compiler will be submitted to the Khronos Group for conformance testing prior to its final release.
+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

@@ -12,64 +12,74 @@
     <remote name="gpuopen-tools"
             fetch="https://github.com/GPUOpen-Tools/" />
 
-    <default revision="refs/tags/roc-2.9.0"
+    <default revision="refs/tags/rocm-3.3.0"
              remote="roc-github"
              sync-c="true"
              sync-j="4" />
 
-    <project name="ROCK-Kernel-Driver" />
-    <project name="ROCT-Thunk-Interface" />
+    <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" />
+    <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-2.9.0" />
-    <project name="roctracer" remote="rocm-devtools" revision="roc-2.9.x" />
+
+    <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" />
-    <project path="ROCm-OpenCL-Runtime/compiler/driver" name="ROCm-OpenCL-Driver"/>
-    <project path="ROCm-OpenCL-Runtime/compiler/llvm" name="llvm" revision="refs/tags/roc-ocl-2.9.0" />
-    <project path="ROCm-OpenCL-Runtime/compiler/llvm/tools/clang" name="clang" />
-    <project path="ROCm-OpenCL-Runtime/compiler/llvm/tools/lld" name="lld" revision="refs/tags/roc-ocl-2.9.0" />
-    <project path="ROCm-OpenCL-Runtime/library/amdgcn" name="ROCm-Device-Libs" revision="refs/tags/roc-ocl-2.9.0" />
-    <project path="ROCm-OpenCL-Runtime/api/opencl/khronos/icd" name="OpenCL-ICD-Loader" remote="KhronosGroup" revision="6c03f8b58fafd9dd693eaac826749a5cfad515f8" />
+    <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" revision="refs/tags/roc-hcc-2.9.0" />
+    <project name="hcc" sync-s="true" />
     <project name="HCC-Example-Application" remote="rocm-devtools" revision="ffd6533305e79eed667badd3c4cdb7879a1281b8" />
-    <project name="HIP" remote="rocm-devtools" revision="refs/tags/roc-2.9.0" />
+    <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" path="llvm_amd-common" revision="refs/tags/roc-ocl-2.9.0" />
-    <project name="lld" path="llvm_amd-common/lld" revision="refs/tags/roc-ocl-2.9.0" />
-    <project name="clang" path="llvm_amd-common/clang" />
-    <project name="ROCm-Device-Libs" revision="roc-2.9.x" />
-    <project name="atmi" revision="refs/tags/rocm_2.9.0" />
+    <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" />
+    <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" revision="refs/tags/rocm-2.9" />
-    <project name="hipBLAS" remote="rocm-swplat" revision="refs/tags/rocm-2.9" />
-    <project name="rocFFT" remote="rocm-swplat" revision="refs/tags/rocm-2.9" />
-    <project name="rocRAND" remote="rocm-swplat" revision="refs/tags/2.9.0" />
-    <project name="rocSPARSE" remote="rocm-swplat" revision="refs/tags/rocm-2.9" />
-    <project name="hipSPARSE" remote="rocm-swplat" revision="refs/tags/rocm-2.9" />
-    <project name="rocALUTION" remote="rocm-swplat" revision="refs/tags/rocm-2.9" />
-    <project name="MIOpenGEMM" remote="rocm-swplat" revision="6275a879995b58a6e0b8cca7b1ad8421a5e02ade" />
-    <project name="MIOpen" remote="rocm-swplat" revision="refs/tags/roc-2.9.0" />
-    <project name="rocm_smi_lib" />
-    <project name="rccl" remote="rocm-swplat" revision="refs/tags/2.9.0" />
-    <project name="MIVisionX" remote="gpuopen-libs" revision="refs/tags/1.3.0" />
-    <project name="rocThrust" remote="rocm-swplat" revision="refs/tags/2.9.0" />
-    <project name="hipCUB" remote="rocm-swplat" revision="refs/tags/2.9.0" />
-    <project name="rocPRIM" remote="rocm-swplat" revision="refs/tags/2.9.0" />
+    <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>

version_history.md

@@ -1,7 +1,11 @@
 ## ROCm Version History
 This file contains archived version history information for the [ROCm project](https://github.com/RadeonOpenCompute/ROCm)
 
-### Current ROCm Version: 2.9
+### 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)
@@ -21,6 +25,89 @@ This file contains archived version history information for the [ROCm project](h
 - [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