SWDEV-444835 - Rocm 6.1 HIP Docs Update

Change-Id: I507ca98594f9246ae96e267f7dd1ed0c615ee055

README.md

@@ -7,7 +7,7 @@ Key features include:
 * HIP is very thin and has little or no performance impact over coding directly in CUDA mode.
 * HIP allows coding in a single-source C++ programming language including features such as templates, C++11 lambdas, classes, namespaces, and more.
 * HIP allows developers to use the "best" development environment and tools on each target platform.
-* The [HIPIFY](https://github.com/ROCm-Developer-Tools/HIPIFY/blob/amd-staging/README.md) tools automatically convert source from CUDA to HIP.
+* The [HIPIFY](https://github.com/ROCm/HIPIFY/blob/amd-staging/README.md) tools automatically convert source from CUDA to HIP.
 * Developers can specialize for the platform (CUDA or AMD) to tune for performance or handle tricky cases.
 
 New projects can be developed directly in the portable HIP C++ language and can run on either NVIDIA or AMD platforms.  Additionally, HIP provides porting tools which make it easy to port existing CUDA codes to the HIP layer, with no loss of performance as compared to the original CUDA application.  HIP is not intended to be a drop-in replacement for CUDA, and developers should expect to do some manual coding and performance tuning work to complete the port.
@@ -45,17 +45,17 @@ HIP releases are typically naming convention for each ROCM release to help diffe
 - [HIP Debugging ](docs/how_to_guides/debugging.md)
 - [HIP RTC](docs/user_guide/hip_rtc.md)
 - [HIP Terminology](docs/reference/terms.md) (including Rosetta Stone of GPU computing terms across CUDA/HIP/OpenCL)
-- [HIPIFY](https://github.com/ROCm-Developer-Tools/HIPIFY/blob/amd-staging/README.md)
+- [HIPIFY](https://github.com/ROCm/HIPIFY/blob/amd-staging/README.md)
 - Supported CUDA APIs:
-  * [Runtime API](https://github.com/ROCm-Developer-Tools/HIPIFY/blob/master/doc/markdown/CUDA_Runtime_API_functions_supported_by_HIP.md)
-  * [Driver API](https://github.com/ROCm-Developer-Tools/HIPIFY/blob/master/doc/markdown/CUDA_Driver_API_functions_supported_by_HIP.md)
-  * [cuComplex API](https://github.com/ROCm-Developer-Tools/HIPIFY/blob/master/doc/markdown/cuComplex_API_supported_by_HIP.md)
-  * [Device API](https://github.com/ROCm-Developer-Tools/HIPIFY/blob/master/doc/markdown/CUDA_Device_API_supported_by_HIP.md)
-  * [cuBLAS](https://github.com/ROCm-Developer-Tools/HIPIFY/blob/master/doc/markdown/CUBLAS_API_supported_by_HIP.md)
-  * [cuRAND](https://github.com/ROCm-Developer-Tools/HIPIFY/blob/master/doc/markdown/CURAND_API_supported_by_HIP.md)
-  * [cuDNN](https://github.com/ROCm-Developer-Tools/HIPIFY/blob/master/doc/markdown/CUDNN_API_supported_by_HIP.md)
-  * [cuFFT](https://github.com/ROCm-Developer-Tools/HIPIFY/blob/master/doc/markdown/CUFFT_API_supported_by_HIP.md)
-  * [cuSPARSE](https://github.com/ROCm-Developer-Tools/HIPIFY/blob/master/doc/markdown/CUSPARSE_API_supported_by_HIP.md)
+  * [Runtime API](https://github.com/ROCm/HIPIFY/blob/amd-staging/docs/tables/CUDA_Runtime_API_functions_supported_by_HIP.md)
+  * [Driver API](https://github.com/ROCm/HIPIFY/blob/amd-staging/docs/tables/CUDA_Driver_API_functions_supported_by_HIP.md)
+  * [cuComplex API](https://github.com/ROCm/HIPIFY/blob/amd-staging/docs/tables/cuComplex_API_supported_by_HIP.md)
+  * [Device API](https://github.com/ROCm/HIPIFY/blob/amd-staging/docs/tables/CUDA_Device_API_supported_by_HIP.md)
+  * [cuBLAS](https://github.com/ROCm/HIPIFY/blob/amd-staging/docs/tables/CUBLAS_API_supported_by_ROC.md)
+  * [cuRAND](https://github.com/ROCm/HIPIFY/blob/amd-staging/docs/tables/CURAND_API_supported_by_HIP.md)
+  * [cuDNN](https://github.com/ROCm/HIPIFY/blob/amd-staging/docs/tables/CUDNN_API_supported_by_HIP.md)
+  * [cuFFT](https://github.com/ROCm/HIPIFY/blob/amd-staging/docs/tables/CUFFT_API_supported_by_HIP.md)
+  * [cuSPARSE](https://github.com/ROCm/HIPIFY/blob/amd-staging/docs/tables/CUSPARSE_API_supported_by_HIP.md)
 - [Developer/CONTRIBUTING Info](docs/developer_guide/contributing.md)
 - [Release Notes](RELEASE.md)
 
@@ -115,28 +115,28 @@ HIP C++ code can be compiled with either,
   profiler and debugger.
 - On the AMD ROCm platform, HIP provides a header and runtime library built on top of HIP-Clang compiler.  The HIP runtime implements HIP streams, events, and memory APIs,
   and is a object library that is linked with the application.  The source code for all headers and the library implementation is available on GitHub.
-  HIP developers on ROCm can use AMD's ROCgdb (https://github.com/ROCm-Developer-Tools/ROCgdb) for debugging and profiling.
+  HIP developers on ROCm can use AMD's ROCgdb (https://github.com/ROCm/ROCgdb) for debugging and profiling.
 
 Thus HIP source code can be compiled to run on either platform.  Platform-specific features can be isolated to a specific platform using conditional compilation.  Thus HIP
 provides source portability to either platform.   HIP provides the _hipcc_ compiler driver which will call the appropriate toolchain depending on the desired platform.
 
 
 ## Examples and Getting Started:
 
-* A sample and [blog](https://github.com/ROCm-Developer-Tools/hip-tests/tree/develop/samples/0_Intro/square) that uses any of [HIPIFY](https://github.com/ROCm-Developer-Tools/HIPIFY/blob/amd-staging/README.md) tools to convert a simple app from CUDA to HIP:
+* A sample and [blog](https://github.com/ROCm/hip-tests/tree/develop/samples/0_Intro/square) that uses any of [HIPIFY](https://github.com/ROCm/HIPIFY/blob/amd-staging/README.md) tools to convert a simple app from CUDA to HIP:
 
 
 ```shell
 cd samples/01_Intro/square
 # follow README / blog steps to hipify the application.
 ```
 
-* Guide to [Porting a New Cuda Project](docs/user_guide/hip_porting_guide.md/"Porting a New CUDA Project")
+* Guide to [Porting a New Cuda Project](https://rocm.docs.amd.com/projects/HIP/en/latest/user_guide/hip_porting_guide.html#porting-a-new-cuda-project)
 
 
 ## More Examples
-The GitHub repository [HIP-Examples](https://github.com/ROCm-Developer-Tools/HIP-Examples) contains a hipified version of benchmark suite.
-Besides, there are more samples in Github [HIP samples](https://github.com/ROCm-Developer-Tools/hip-tests/tree/develop/samples), showing how to program with different features, build and run.
+The GitHub repository [HIP-Examples](https://github.com/ROCm/HIP-Examples) contains a hipified version of benchmark suite.
+Besides, there are more samples in Github [HIP samples](https://github.com/ROCm/hip-tests/tree/develop/samples), showing how to program with different features, build and run.
 
 ## Tour of the HIP Directories
 * **include**:
@@ -151,6 +151,6 @@ Besides, there are more samples in Github [HIP samples](https://github.com/ROCm-
 * **docs**: Documentation - markdown and doxygen info.
 
 ## Reporting an issue
-Use the [GitHub issue tracker](https://github.com/ROCm-Developer-Tools/HIP/issues).
+Use the [GitHub issue tracker](https://github.com/ROCm/HIP/issues).
 If reporting a bug, include the output of "hipconfig --full" and samples/1_hipInfo/hipInfo (if possible).
 

RELEASE.md

@@ -1,6 +1,6 @@
 # Release notes
 
-We have attempted to document known bugs and limitations - in particular the [HIP Kernel Language](docs/markdown/hip_kernel_language.md) document uses the phrase "Under Development", and the [HIP Runtime API bug list](http://rocm-developer-tools.github.io/HIP/bug.html) lists known bugs. 
+We have attempted to document known bugs and limitations - in particular the [HIP Kernel Language](docs/markdown/hip_kernel_language.md) document uses the phrase "Under Development", and the [HIP Runtime API issue list](https://github.com/ROCm/HIP/issues) lists known bugs. 
 
 
 ===================================================================================================
@@ -155,7 +155,7 @@ Date: 2016.06.06
 - Add cross-linking support between G++ and HCC, in particular for interfaces that use
   standard C++ libraries (ie std::vectors, std::strings).  HIPCC now uses libstdc++ by default on the HCC
   compilation path.
-- More samples including gpu-burn, SHOC, nbody, rtm.  See [HIP-Examples](https://github.com/ROCm-Developer-Tools/HIP-Examples)
+- More samples including gpu-burn, SHOC, nbody, rtm.  See [HIP-Examples](https://github.com/ROCm/HIP-Examples)
 
 
 ===================================================================================================

docs/developer_guide/build.md

@@ -23,9 +23,9 @@ Install Nvidia driver and pre-build packages (see HIP Installation Guide at http
 ### Branch of repository
 
 Before get HIP source code, set the expected branch of repository at the variable `ROCM_BRANCH`.
-For example, for ROCm6.0 release branch, set
+For example, for ROCm 6.1 release branch, set
 ```shell
-export ROCM_BRANCH=rocm-6.0.x
+export ROCM_BRANCH=rocm-6.1.x
 ```
 
 ROCm5.7 release branch, set
@@ -37,29 +37,35 @@ Similiar format for future branches.
 `ROCM_PATH` is path where ROCM is installed. BY default `ROCM_PATH` is at `/opt/rocm`.
 
 
-## Build HIP on AMD platform
+## Build HIP
 
 
 ### Get HIP source code
 
+A new repository 'hipother' is added in the ROCm 6.1 release, which is branched out from HIP.
+The 'hipother' provides files required to support the HIP back-end implementation on some non-AMD platforms, like NVIDIA.
+
 ```shell
-git clone -b "$ROCM_BRANCH" https://github.com/ROCm-Developer-Tools/clr.git
-git clone -b "$ROCM_BRANCH" https://github.com/ROCm-Developer-Tools/hip.git
-git clone -b "$ROCM_BRANCH" https://github.com/ROCm-Developer-Tools/HIPCC.git
+git clone -b "$ROCM_BRANCH" https://github.com/ROCm/clr.git
+git clone -b "$ROCM_BRANCH" https://github.com/ROCm/hip.git
+git clone -b "$ROCM_BRANCH" https://github.com/ROCm/hipother.git
+git clone -b "$ROCM_BRANCH" https://github.com/ROCm/HIPCC.git hipcc
 ```
 
 ### Set the environment variables
 
 ```shell
 export CLR_DIR="$(readlink -f clr)"
 export HIP_DIR="$(readlink -f hip)"
+export HIP_OTHER="$(readlink -f hipother)"
 export HIPCC_DIR="$(readlink -f hipcc)"
 ```
 
 Note, starting from ROCM 5.6 release, clr is a new repository including the previous ROCclr, HIPAMD and OpenCl repositories.
 ROCclr is defined on AMD platform that HIP uses Radeon Open Compute Common Language Runtime (ROCclr), which is a virtual device interface that HIP runtimes interact with different backends.
-HIPAMD provides implementation specifically for AMD platform.
+HIPAMD provides implementation specifically for the AMD platform.
 OpenCL provides headers that ROCclr runtime currently depends on.
+hipother provides headers and implementation specifically for the non-AMD platform, like NVIDIA.
 
 ### Build the HIPCC runtime
 
@@ -70,13 +76,15 @@ cmake ..
 make -j4
 ```
 
-### Build HIP
+### Build HIP on the AMD platform
+
+#### Build HIP runtime
+Commands to build HIP runtime on the AMD platform are as following. The option 'HIP_PLATFORM=amd' should be defined.
 
 ```shell
 cd "$CLR_DIR"
 mkdir -p build; cd build
 cmake -DHIP_COMMON_DIR=$HIP_DIR -DHIP_PLATFORM=amd -DCMAKE_PREFIX_PATH="/opt/rocm/" -DCMAKE_INSTALL_PREFIX=$PWD/install -DHIPCC_BIN_DIR=$HIPCC_DIR/build -DHIP_CATCH_TEST=0 -DCLR_BUILD_HIP=ON -DCLR_BUILD_OCL=OFF ..
-
 make -j$(nproc)
 sudo make install
 ```
@@ -85,7 +93,7 @@ Note, if `CMAKE_INSTALL_PREFIX` is not specified, hip runtime will be installed
 By default, release version of HIP is built.
 
 
-### Default paths and environment variables
+#### Default paths and environment variables
 
    * By default HIP looks for HSA in `<ROCM_PATH>/hsa` (can be overridden by setting `HSA_PATH` environment variable).
    * By default HIP is installed into `<ROCM_PATH>/hip`.
@@ -94,7 +102,7 @@ By default, release version of HIP is built.
    * Optionally, consider adding `<ROCM_PATH>/bin` to your `PATH` to make it easier to use the tools.
    * Optionally, set `HIPCC_VERBOSE=7` to output the command line for compilation.
 
-### Generating profiling header after adding/changing a HIP API
+#### Generate profiling header after adding/changing a HIP API
 
 When you add or change a HIP API, you must generate a new `hip_prof_str.h` header. ROCm tools like ROCProfiler and ROCTracer use this header to track HIP APIs.
 To generate the header after your change, use the tool `hip_prof_gen.py` present in `hipamd/src`.
@@ -119,16 +127,16 @@ hip_prof_gen.py -v -p -t --priv <hip>/include/hip/hip_runtime_api.h \
 <hipamd>/include/hip/amd_detail/hip_prof_str.h.new
 ```
 
-### Build HIP tests
+#### Build HIP tests
 
-HIP catch tests, with new architectured Catch2, are official seperated from HIP project, exist in HIP tests repository, can be built via the following instructions.
+HIP catch tests, with the newly architectured Catch2, are officially separated from the HIP project. The HIP catch tests are moved to the HIP tests repository and can be built using the  instructions in the following sections.
 
-#### Get HIP tests source code
+##### Get HIP tests source code
 
 ```shell
-git clone -b "$ROCM_BRANCH" https://github.com/ROCm-Developer-Tools/hip-tests.git
+git clone -b "$ROCM_BRANCH" https://github.com/ROCm/hip-tests.git
 ```
-#### Build HIP tests from source
+##### Build HIP tests from source
 
 ```shell
 export HIPTESTS_DIR="$(readlink -f hip-tests)"
@@ -156,9 +164,9 @@ cd $HIPTESTS_DIR/build/catch_tests/unit/texture
 ./TextureTest
 ```
 
-#### Build HIP Catch2 standalone test
+##### Build HIP Catch2 standalone tests
 
-HIP Catch2 supports build a standalone test, for example,
+HIP Catch2 supports building standalone tests, for example,
 
 ```shell
 cd "$HIPTESTS_DIR"
@@ -169,48 +177,24 @@ hipcc $HIPTESTS_DIR/catch/unit/memory/hipPointerGetAttributes.cc -I ./catch/incl
 All tests passed
 ```
 
-## Build HIP on NVIDIA platform
-
-
-### Get HIP source code
-
-```shell
-git clone -b "$ROCM_BRANCH" https://github.com/ROCm-Developer-Tools/hip.git
-git clone -b "$ROCM_BRANCH" https://github.com/ROCm-Developer-Tools/clr.git
-git clone -b "$ROCM_BRANCH" https://github.com/ROCm-Developer-Tools/HIPCC.git
-```
-
-### Set the environment variables
-
-```shell
-export HIP_DIR="$(readlink -f hip)"
-export CLR_DIR="$(readlink -f hipamd)"
-export HIPCC_DIR="$(readlink -f hipcc)"
-```
-
-### Build the HIPCC runtime
+### Build HIP on the NVIDIA platform
 
-```shell
-cd "$HIPCC_DIR"
-mkdir -p build; cd build
-cmake ..
-make -j4
-```
 
-### Build HIP
+#### Build HIP runtime
+Commands to build HIP on the NVIDIA platform are as following. The options 'HIPNV_DIR=$HIP_OTHER/hipnv' and 'HIP_PLATFORM=nvidia' should be defined.
 
 ```shell
 cd "$CLR_DIR"
 mkdir -p build; cd build
-cmake -DHIP_COMMON_DIR=$HIP_DIR -DHIP_PLATFORM=nvidia -DCMAKE_INSTALL_PREFIX=$PWD/install -DHIPCC_BIN_DIR=$HIPCC_DIR/build -DHIP_CATCH_TEST=0 -DCLR_BUILD_HIP=ON -DCLR_BUILD_OCL=OFF ..
+cmake -DHIP_COMMON_DIR=$HIP_DIR -DCMAKE_PREFIX_PATH="/opt/rocm/" -DCMAKE_INSTALL_PREFIX=$PWD/install -DHIPCC_BIN_DIR=$HIPCC_DIR/build -DHIP_CATCH_TEST=0 -DCLR_BUILD_HIP=ON -DCLR_BUILD_OCL=OFF -DHIPNV_DIR=$HIP_OTHER/hipnv -DHIP_PLATFORM=nvidia ..
 make -j$(nproc)
 sudo make install
 ```
 
-### Build HIP tests
+#### Build HIP tests
 Build HIP tests commands on NVIDIA platform are basically the same as AMD, except set `-DHIP_PLATFORM=nvidia`.
 
 ## Run HIP
 
-Compile and run the [square sample](https://github.com/ROCm-Developer-Tools/hip-tests/tree/rocm-5.5.x/samples/0_Intro/square).
+Compile and run the [square sample](https://github.com/ROCm/hip-tests/tree/rocm-6.0.x/samples/0_Intro/square).
 

docs/developer_guide/contributing.md

@@ -59,7 +59,7 @@ Selected multilib: .;@m64
 
 ## Unit Testing Environment
 
-Tests for HIP are hosted at [ROCm-Developer-Tools/hip-tests](https://github.com/ROCm-Developer-Tools/hip-tests).
+Tests for HIP are hosted at [ROCm/hip-tests](https://github.com/ROCm/hip-tests).
 
 To run `hip-tests` please go to the repo and follow the steps.
 
@@ -124,7 +124,7 @@ Differences or limitations of HIP APIs as compared to CUDA APIs should be clearl
 
 
 ### Presubmit Testing:
-Before checking in or submitting a pull request, run all hip-tests (see [ROCm-Developer-Tools/hip-tests](https://github.com/ROCm-Developer-Tools/hip-tests)).
+Before checking in or submitting a pull request, run all hip-tests (see [ROCm/hip-tests](https://github.com/ROCm/hip-tests)).
 
 
 ### Checkin messages

docs/doxygen/Doxyfile

@@ -2193,7 +2193,8 @@ INCLUDE_FILE_PATTERNS  =
 # recursively expanded use the := operator instead of the = operator.
 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
 
-PREDEFINED             = __HIP_PLATFORM_AMD__
+PREDEFINED             = __HIP_PLATFORM_AMD__ \
+                         __dparm(x)=
 
 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
 # tag can be used to specify a list of macro names that should be expanded. The

docs/doxygen/mainpage.md

@@ -18,7 +18,6 @@ This is the full HIP Runtime API reference. The API is organized into
   - @ref StreamO
 - @ref PeerToPeer
 - @ref Context
-  - @ref ContextD
 - @ref Module
 - @ref Occupancy
 - @ref Profiler

docs/how_to_guides/debugging.md

@@ -79,7 +79,7 @@ PASSED!
 ### Using ROCgdb
 HIP developers on ROCm can use AMD's ROCgdb for debugging and profiling.
 ROCgdb is the ROCm source-level debugger for Linux, based on GDB, the GNU source-level debugger, equivalent of cuda-gdb, can be used with debugger frontends, such as eclipse, vscode, or gdb-dashboard.
-For details, see (https://github.com/ROCm-Developer-Tools/ROCgdb).
+For details, see (https://github.com/ROCm/ROCgdb).
 
 Below is a sample how to use ROCgdb run and debug HIP application, rocgdb is installed with ROCM package in the folder /opt/rocm/bin.
 
@@ -91,7 +91,7 @@ Copyright (C) 2020 Free Software Foundation, Inc.
 License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
 ...
 For bug reporting instructions, please see:
-<https://github.com/ROCm-Developer-Tools/ROCgdb/issues>.
+<https://github.com/ROCm/ROCgdb/issues>.
 Find the GDB manual and other documentation resources online at:
     <http://www.gnu.org/software/gdb/documentation/>.
 

docs/reference/deprecated_api_list.md

@@ -20,6 +20,11 @@ CUDA supports cuCtx API, the Driver API that defines "Context" and "Devices" as
 ### hipCtxGetFlags
 ### hipCtxEnablePeerAccess
 ### hipCtxDisablePeerAccess
+### hipDevicePrimaryCtxGetState
+### hipDevicePrimaryCtxRelease
+### hipDevicePrimaryCtxRetain
+### hipDevicePrimaryCtxReset
+### hipDevicePrimaryCtxSetFlags
 
 
 ## HIP Memory Management APIs
@@ -52,16 +57,12 @@ Should use roctracer/rocTX instead
 ## HIP Texture Management APIs
 
 ### hipGetTextureReference
+### hipGetTextureAlignmentOffset
 ### hipTexRefSetAddressMode
 ### hipTexRefSetArray
 ### hipTexRefSetFilterMode
 ### hipTexRefSetFlags
 ### hipTexRefSetFormat
-### hipBindTexture
-### hipBindTexture2D
-### hipBindTextureToArray
-### hipGetTextureAlignmentOffset
-### hipUnbindTexture
 ### hipTexRefGetAddress
 ### hipTexRefGetAddressMode
 ### hipTexRefGetFilterMode
@@ -80,4 +81,10 @@ Should use roctracer/rocTX instead
 ### hipTexRefSetMipmapLevelBias
 ### hipTexRefSetMipmapLevelClamp
 ### hipTexRefSetMipmappedArray
+### hipTexRefGetBorderColor
+### hipTexRefGetArray
+### hipBindTexture
+### hipBindTexture2D
+### hipBindTextureToArray
+### hipUnbindTexture
 ### hipBindTextureToMipmappedArray

docs/reference/glossary.md

@@ -10,10 +10,13 @@ The default device can be set with hipSetDevice.
 
 - HIP-Clang - Heterogeneous AMDGPU Compiler, with its capability to compile HIP programs on AMD platform (https://github.com/RadeonOpenCompute/llvm-project).
 
-- ROCclr - a virtual device interface that compute runtimes interact with different backends such as ROCr on Linux or PAL on Windows.
-  The ROCclr (https://github.com/ROCm-Developer-Tools/ROCclr) is an abstraction layer allowing runtimes to work on both OSes without much effort.
+- clr - a repository for AMD Common Language Runtime, contains source codes for AMD's compute languages runtimes: HIP and OpenCL™.
+clr (https://github.com/ROCm/clr) contains the following three parts,
+hipamd: contains implementation of HIP language on AMD platform.
+rocclr: contains common runtime used in HIP and OpenCL™, which provides virtual device interfaces that compute runtimes interact with different backends such as ROCr on Linux or PAL on Windows.
+opencl: contains implementation of OpenCL™ on AMD platform.
 
-- hipify tools - tools to convert CUDA code to portable C++ code (https://github.com/ROCm-Developer-Tools/HIPIFY).
+- hipify tools - tools to convert CUDA code to portable C++ code (https://github.com/ROCm/HIPIFY).
 
 - hipconfig - tool to report various configuration properties of the target platform.