Merge branch 'develop' into roc-6.0.x

* Update changelog announcement

* Update phrasing

.github/CODEOWNERS

@@ -1 +1,5 @@
 * @saadrahim @Rmalavally @amd-aakash @zhang2amd @jlgreathouse @samjwu @MathiasMagnus @LisaDelaney
+# Documentation files
+docs/* @ROCm/rocm-documentation
+*.md @ROCm/rocm-documentation
+*.rst @ROCm/rocm-documentation

.github/ISSUE_TEMPLATE/1_feature_request.yml

@@ -1,32 +0,0 @@
-name: Feature Suggestion
-description: Suggest an additional functionality, or new way of handling an existing functionality.
-title: "[Feature]: "
-
-body:
-- type: markdown
-  attributes:
-    value: |
-      Thank you for taking the time to make a suggestion!
-
-- type: textarea
-  attributes:
-    label: Suggestion Description
-    description: Describe your suggestion.
-  validations:
-    required: true
-- type: input
-  attributes:
-    label: Operating System
-    description: (Optional) If this is for a specific OS, you can mention it here.
-    placeholder: "e.g. Ubuntu"
-- type: input
-  attributes:
-    label: GPU
-    description: (Optional) If this is for a specific GPU or GPU family, you can mention it here.
-    placeholder: "e.g. MI200"
-- type: input
-  attributes:
-    label: ROCm Component
-    description: (Optional) If this issue relates to a specific ROCm component, it can be mentioned here.
-    placeholder: "e.g. rocBLAS"
-

.github/ISSUE_TEMPLATE/config.yml

@@ -1 +0,0 @@
-blank_issues_enabled: true

.github/ISSUE_TEMPLATE/issue_report.yml

@@ -1,180 +0,0 @@
-name: Issue Report
-description: File a report for ROCm related issues on Linux and Windows. For issues pertaining to documentation or non-bug related, please open a blank issue located below.
-title: "[Issue]: "
-
-body:
-- type: markdown
-  attributes:
-    value: |
-      Thank you for taking the time to fill out this report!
-
-      You can acquire your OS, CPU, GPU (for filling out this report) with the following commands:
-
-      Linux:
-        echo "OS:" && cat /etc/os-release | grep -E "^(NAME=|VERSION=)";
-        echo "CPU: " && cat /proc/cpuinfo | grep "model name" | sort --unique;
-        echo "GPU:" && /opt/rocm/bin/rocminfo | grep -E "^\s*(Name|Marketing Name)";
-        
-      Windows:
-         (Get-WmiObject Win32_OperatingSystem).Version
-         (Get-WmiObject win32_Processor).Name
-         (Get-WmiObject win32_VideoController).Name
-- type: textarea
-  attributes:
-    label: Problem Description
-    description: Describe the issue you encountered.
-  validations:
-    required: true
-- type: input
-  attributes:
-    label: Operating System
-    description: What is the name and version number of the OS?
-    placeholder: "e.g. Ubuntu 22.04.3 LTS (Jammy Jellyfish)"
-  validations:
-    required: true
-- type: input
-  attributes:
-    label: CPU
-    description: What CPU did you encounter the issue on?
-    placeholder: "e.g. AMD Ryzen 9 5900HX with Radeon Graphics"
-  validations:
-    required: true
-- type: dropdown
-  attributes:
-    label: GPU
-    description: What GPU(s) did you encounter the issue on (you can select multiple GPUs from the list)
-    multiple: true
-    options:
-        - AMD Instinct MI300
-        - AMD Instinct MI300A
-        - AMD Instinct MI300X
-        - AMD Instinct MI250X
-        - AMD Instinct MI250
-        - AMD Instinct MI210
-        - AMD Instinct MI100
-        - AMD Instinct MI50
-        - AMD Instinct MI25
-        - AMD Radeon Pro V620
-        - AMD Radeon Pro VII
-        - AMD Radeon RX 7900 XTX
-        - AMD Radeon VII
-        - AMD Radeon Pro W7900
-        - AMD Radeon Pro W7800
-        - AMD Radeon Pro W6800
-        - AMD Radeon Pro W6600
-        - AMD Radeon Pro W5500
-        - AMD Radeon RX 7900 XT
-        - AMD Radeon RX 7600
-        - AMD Radeon RX 6950 XT
-        - AMD Radeon RX 6900 XT
-        - AMD Radeon RX 6800 XT
-        - AMD Radeon RX 6800
-        - AMD Radeon RX 6750
-        - AMD Radeon RX 6700 XT
-        - AMD Radeon RX 6700
-        - AMD Radeon RX 6650 XT
-        - AMD Radeon RX 6600 XT
-        - AMD Radeon RX 6600
-        - Other
-  validations:
-    required: true
-- type: input
-  attributes:
-    label: Other
-    description: If you selected Other, please specify
-- type: dropdown
-  attributes:
-    label: ROCm Version
-    description: What version(s) of ROCm did you encounter the issue on?
-    multiple: true
-    options:
-        - ROCm 6.0.0
-        - ROCm 5.7.1
-        - ROCm 5.7.0
-        - ROCm 5.6.0
-        - ROCm 5.5.1
-        - ROCm 5.5.0
-  validations:
-    required: true
-- type: dropdown
-  attributes:
-    label: ROCm Component
-    description: (Optional) If this issue relates to a specific ROCm component, it can be mentioned here.
-    options:
-      - Other
-      - AMDMIGraphX
-      - amdsmi
-      - aomp
-      - aomp-extras
-      - clang-ocl
-      - clr
-      - composable_kernel
-      - flang
-      - half
-      - HIP
-      - hipBLAS
-      - HIPCC
-      - hipCUB
-      - HIP-Examples
-      - hipFFT
-      - hipfort
-      - HIPIFY
-      - hipSOLVER
-      - hipSPARSE
-      - hipTensor
-      - llvm-project
-      - MIOpen
-      - MIVisionX
-      - rccl
-      - rdc
-      - rocALUTION
-      - rocBLAS
-      - ROCdbgapi
-      - rocFFT
-      - ROCgdb
-      - ROCK-Kernel-Driver
-      - ROCm
-      - rocm_bandwidth_test
-      - rocm_smi_lib
-      - rocm-cmake
-      - ROCm-CompilerSupport
-      - rocm-core
-      - ROCm-Device-Libs
-      - rocminfo
-      - rocMLIR
-      - ROCmValidationSuite
-      - rocPRIM
-      - rocprofiler
-      - rocr_debug_agent
-      - rocRAND
-      - ROCR-Runtime
-      - rocSOLVER
-      - rocSPARSE
-      - rocThrust
-      - roctracer
-      - ROCT-Thunk-Interface
-      - rocWMMA
-      - rpp
-      - Tensile
-    default: 32
-- type: textarea
-  attributes:
-    label: Steps to Reproduce
-    description: (Optional) Detailed steps to reproduce the issue.
-  validations:
-    required: false
-    
-- type: textarea
-  attributes:
-    label: (Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
-    description: The output of rocminfo --support could help to better address the problem.
-  validations:
-    required: false
-
-- type: textarea
-  attributes:
-    label: Additional Information
-    description: (Optional) Any additional information that is relevant, e.g. relevant environment variables, dockerfiles, log files, dmesg output (on Linux), etc.
-  validations:
-    required: false
-    

.github/workflows/issue_retrieval.yml

@@ -0,0 +1,22 @@
+name: Issue retrieval
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  auto-retrieve:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Generate a token
+        id: generate_token
+        uses: actions/create-github-app-token@v1
+        with:
+          app_id: ${{ secrets.ACTION_APP_ID }}
+          private_key: ${{ secrets.ACTION_PEM }}
+      - name: 'Retrieve Issue'
+        uses: abhimeda/rocm_issue_management@main
+        with:
+          authentication-token: ${{ steps.generate_token.outputs.token }}
+          github-organization: 'ROCm'
+          project-num: '6'

CONTRIBUTING.md

@@ -8,7 +8,7 @@
 
 AMD values and encourages contributions to our code and documentation. If you want to contribute
 to our ROCm repositories, first review the following guidance. For documentation-specific information,
-see [Contributing to ROCm docs](./contribute-docs.md).
+see [Contributing to ROCm docs](https://rocm.docs.amd.com/en/latest/contribute/contribute-docs.html).
 
 ROCm is a software stack made up of a collection of drivers, development tools, and APIs that enable
 GPU programming from low-level kernel to end-user applications. Because some of our components
@@ -47,14 +47,13 @@ General issue guidelines:
 
 ### Pull requests
 
-Our repositories typically use the **develop** branch an integration branch for new code so, when
-making a PR, target this branch.
+When you create a pull request, you should target the default branch.  Our repositories typically use the **develop** branch as the default integration branch.
 
 When creating a PR, use the following process. Note that each repository may include additional,
 project-specific steps. Refer to each repository's PR process for any additional steps.
 
 * Identify the issue you want to fix
-* Target the **develop** branch for integration
+* Target the default branch (usually the **develop** branch) for integration
 * Ensure your code builds successfully
 * Each component has a suite of test cases to run; include the log of the successful test run in your PR
 * Do not break existing test cases
@@ -73,7 +72,7 @@ terms of the LICENSE.txt file in the corresponding repository. Different reposit
 licenses.
 :::
 
-You can look up each license on the [ROCm licensing](../about/licensing.md) page.
+You can look up each license on the [ROCm licensing](https://rocm.docs.amd.com/en/latest/about/license.html) page.
 
 ### New feature development
 

README.md

@@ -34,7 +34,7 @@ The ROCm documentation homepage is [rocm.docs.amd.com](https://rocm.docs.amd.com
 ### Building our documentation
 
 For a quick-start build, use the following code. For more options and detail, refer to
-[Building documentation](./contribute/building.md).
+[Building documentation](./docs/contribute/building.md).
 
 ```bash
 cd docs

RELEASE.md

@@ -1,248 +1,54 @@
-# Release notes for AMD ROCm™ 6.0
-
-ROCm 6.0 is a major release with new performance optimizations, expanded frameworks and library
-support, and improved developer experience. This includes initial enablement of the AMD Instinct™
-MI300 series. Future releases will further enable and optimize this new platform. Key features include:
-
-* Improved performance in areas like lower precision math and attention layers.
-* New hipSPARSELt library accelerates AI workloads via AMD's sparse matrix core technique.
-* Upstream support is now available for popular AI frameworks like TensorFlow, JAX, and PyTorch.
-* New support for libraries, such as DeepSpeed, ONNX-RT, and CuPy.
-* Prepackaged HPC and AI containers on AMD Infinity Hub, with improved documentation and
-  tutorials on the [AMD ROCm Docs](https://rocm.docs.amd.com) site.
-* Consolidated developer resources and training on the new
-  [AMD ROCm Developer Hub](https://www.amd.com/en/developer/resources/rocm-hub.html).
-
-The following section provide a release overview for ROCm 6.0. For additional details, you can refer to
-the [Changelog](https://rocm.docs.amd.com/en/develop/about/CHANGELOG.html). We list known
-issues on [GitHub](https://github.com/ROCm/ROCm/issues).
-
-## OS and GPU support changes
-
-ROCm 6.0 enables the use of MI300A and MI300X Accelerators with a limited operating systems
-support. Future releases will add additional OS's to match our general offering.
-
-| Operating Systems | MI300A | MI300X |
-|:---:|:---:|:---:|
-| Ubuntu 22.04.3 | Supported | Supported |
-| RHEL 8.9 | Supported |  |
-| SLES15 SP5 | Supported |  |
-
-For older generations of supported Instinct products we've added the following operating systems:
-
-* RHEL 9.3
-* RHEL 8.9
-
-Note: For ROCm 6.2 and beyond, we've planned for end-of-support (EoS) for the following operating
-systems:
-
-* Ubuntu 20.04.5
-* SLES 15 SP4
-* RHEL/CentOS 7.9
-
-## New ROCm meta package
-
-We've added a new ROCm meta package for easy installation of all ROCm core packages, tools, and
-libraries. For example, the following command will install the full ROCm package: `apt-get install rocm`
-(Ubuntu), or `yum install rocm` (RHEL).
-
-## Filesystem Hierarchy Standard
-
-ROCm 6.0 fully adopts the Filesystem Hierarchy Standard (FHS) reorganization goals. We've removed
-the backward compatibility support for old file locations.
-
-## Compiler location change
-
-* The installation path of LLVM has been changed from `/opt/rocm-<rel>/llvm` to
-  `/opt/rocm-<rel>/lib/llvm`. For backward compatibility, a symbolic link is provided to the old
-  location and will be removed in a future release.
-* The installation path of the device library bitcode has changed from `/opt/rocm-<rel>/amdgcn` to
-  `/opt/rocm-<rel>/lib/llvm/lib/clang/<ver>/lib/amdgcn`. For backward compatibility, a symbolic link
-  is provided and will be removed in a future release.
-
-## Documentation
-
-CMake support has been added for documentation in the
-[ROCm repository](https://github.com/RadeonOpenCompute/ROCm).
-
-## AMD Instinct™ MI50 end-of-support notice
-
-AMD Instinct MI50, Radeon Pro VII, and Radeon VII products (collectively gfx906 GPUs) enters
-maintenance mode in ROCm 6.0.
-
-As outlined in [5.6.0](https://rocm.docs.amd.com/en/docs-5.6.0/release.html), ROCm 5.7 was the
-final release for gfx906 GPUs in a fully supported state.
-
-  * Henceforth, no new features and performance optimizations will be supported for the gfx906 GPUs.
-  * Bug fixes and critical security patches will continue to be supported for the gfx906 GPUs until Q2
-    2024 (end of maintenance \[EOM] will be aligned with the closest ROCm release).
-  * Bug fixes will be made up to the next ROCm point release.
-  * Bug fixes will not be backported to older ROCm releases for gfx906.
-  * Distribution and operating system updates will continue per the ROCm release cadence for gfx906
-    GPUs until EOM.
-
-## ROCm projects
-
-The following sections contains project-specific release notes for ROCm 6.0. For additional details, you
-can refer to the [Changelog](https://rocm.docs.amd.com/en/develop/about/CHANGELOG.html).
-
-### AMD SMI
-
-* **Integrated the E-SMI (EPYC-SMI) library**.
-    You can now query CPU-related information directly through AMD SMI. Metrics include power,
-    energy, performance, and other system details.
-
-* **Added support for gfx942 metrics**.
-    You can now query MI300 device metrics to get real-time information. Metrics include power,
-    temperature, energy, and performance.
-
-### HIP
-
-* **New features to improve resource interoperability**.
-  * For external resource interoperability, we've added new structs and enums.
-  * We've added new members to HIP struct `hipDeviceProp_t` for surfaces, textures, and device
-    identifiers.
-
-* **Changes impacting backward compatibility**.
-    There are several changes impacting backward compatibility: we changed some struct members and
-    some enum values, and removed some deprecated flags. For additional information, please refer to
-    the Changelog.
-
-### hipCUB
-
-* **Additional CUB API support**.
-    The hipCUB backend is updated to CUB and Thrust 2.1.
-
-### HIPIFY
-
-* **Enhanced CUDA2HIP document generation**.
-    API versions are now listed in the CUDA2HIP documentation. To see if the application binary
-    interface (ABI) has changed, refer to the
-    [*C* column](https://rocm.docs.amd.com/projects/HIPIFY/en/latest/tables/CUDA_Runtime_API_functions_supported_by_HIP.html)
-    in our API documentation.
-
-* **Hipified rocSPARSE**.
-    We've implemented support for the direct hipification of additional cuSPARSE APIs into rocSPARSE
-    APIs under the `--roc` option. This covers a major milestone in the roadmap towards complete
-    cuSPARSE-to-rocSPARSE hipification.
-
-### hipRAND
-
-* **Official release**.
-    hipRAND is now a *standalone project*--it's no longer available as a submodule for rocRAND.
-
-### hipTensor
-
-* **Added architecture support**.
-    We've added contraction support for gfx942 architectures, and f32 and f64 data
-    types.
-
-* **Upgraded testing infrastructure**.
-    hipTensor will now support dynamic parameter configuration with input YAML config.
-
-### MIGraphX
-
-* **Added TorchMIGraphX**.
-    We introduced a Dynamo backend for Torch, which allows PyTorch to use MIGraphX directly
-    without first requiring a model to be converted to the ONNX model format. With a single line of
-    code, PyTorch users can utilize the performance and quantization benefits provided by MIGraphX.
-
-* **Boosted overall performance with rocMLIR**.
-    We've integrated the rocMLIR library for ROCm-supported RDNA and CDNA GPUs. This
-    technology provides MLIR-based convolution and GEMM kernel generation.
-
-* **Added INT8 support across the MIGraphX portfolio**.
-    We now support the INT8 data type. MIGraphX can perform the quantization or ingest
-    prequantized models. INT8 support extends to the MIGraphX execution provider for ONNX Runtime.
-
-### ROCgdb
-
-* **Added support for additional GPU architectures**.
-  * Navi 3 series: gfx1100, gfx1101, and gfx1102.
-  * MI300 series: gfx942.
-
-### rocm-smi-lib
-
-* **Improved accessibility to GPU partition nodes**.
-    You can now view, set, and reset the compute and memory partitions. You'll also get notifications of
-    a GPU busy state, which helps you avoid partition set or reset failure.
-
-* **Upgraded GPU metrics version 1.4**.
-    The upgraded GPU metrics binary has an improved metric version format with a content version
-    appended to it. You can read each metric within the binary without the full `rsmi_gpu_metric_t` data
-    structure.
-
-* **Updated GPU index sorting**.
-    We made GPU index sorting consistent with other ROCm software tools by optimizing it to use
-    `Bus:Device.Function` (BDF) instead of the card number.
-
-### ROCm Compiler
-
-* **Added kernel argument optimization on gfx942**.
-    With the new feature, you can preload kernel arguments into Scalar General-Purpose Registers
-    (SGPRs) rather than pass them in memory. This feature is enabled with a compiler option, which also
-    controls the number of arguments to pass in SGPRs. For more information, see:
-    [https://llvm.org/docs/AMDGPUUsage.html#preloaded-kernel-arguments](https://llvm.org/docs/AMDGPUUsage.html#preloaded-kernel-arguments)
-
-* **Improved register allocation at -O0**.
-    We've improved the register allocator used at -O0 to avoid compiler crashes (when the signature is
-    'ran out of registers during register allocation').
-
-* **Improved generation of debug information**.
-    We've improved compile time when generating debug information for certain corner cases. We've
-    also improved the compiler to eliminate compiler crashes when generating debug information.
-
-### ROCmValidationSuite
-
-* **Added GPU and operating system support**.
-    We added support for MI300X GPU in GPU Stress Test (GST).
-
-### Roc Profiler
-
-* **Added option to specify desired Roc Profiler version**.
-    You can now use rocProfV1 or rocProfV2 by specifying your desired version, as the legacy rocProf
-    (`rocprofv1`) provides the option to use the latest version (`rocprofv2`).
-
-* **Automated the ISA dumping process by Advance Thread Tracer**.
-    Advance Thread Tracer (ATT) no longer depends on user-supplied Instruction Set Architecture (ISA)
-    and compilation process (using ``hipcc --save-temps``) to dump ISA from the running kernels.
-
-* **Added ATT support for parallel kernels**.
-    The automatic ISA dumping process also helps ATT successfully parse multiple kernels running in
-    parallel, and provide cycle-accurate occupancy information for multiple kernels at the same time.
-
-### ROCr
-
-* **Support for SDMA link aggregation**.
-    If multiple XGMI links are available when making SDMA copies between GPUs, the copy is
-    distributed over multiple links to increase peak bandwidth.
-
-### rocThrust
-
-* **Added Thrust 2.1 API support**.
-    rocThrust backend is updated to Thrust and CUB 2.1.
-
-### rocWMMA
-
-* **Added new architecture support**.
-    We added support for gfx942 architectures.
-
-* **Added data type support**.
-    We added support for f8, bf8, xf32 data types on supporting architectures, and for bf16 in the HIP RTC
-    environment.
-
-* **Added support for the PyTorch kernel plugin**.
-    We added awareness of `__HIP_NO_HALF_CONVERSIONS__` to support PyTorch users.
-
-### TransferBench (beta)
-
-* **Improved ordering control**.
-    You can now set the thread block size (`BLOCK_SIZE`) and the thread block order (`BLOCK_ORDER`)
-    in which thread blocks from different transfers are run when using a single stream.
-
-* **Added comprehensive reports**.
-    We modified individual transfers to report X Compute Clusters (XCC) ID when `SHOW_ITERATIONS`
-    is set to 1.
-
-* **Improved accuracy in result validation**.
-    You can now validate results for each iteration instead of just once for all iterations.
+# Release notes
+<!-- Disable lints since this is an auto-generated file.    -->
+<!-- markdownlint-disable blanks-around-headers             -->
+<!-- markdownlint-disable no-duplicate-header               -->
+<!-- markdownlint-disable no-blanks-blockquote              -->
+<!-- markdownlint-disable ul-indent                         -->
+<!-- markdownlint-disable no-trailing-spaces                -->
+
+<!-- spellcheck-disable -->
+
+This page contains the release notes for AMD ROCm Software.
+
+-------------------
+
+## ROCm 6.0.2
+
+The ROCm 6.0.2 point release consists of minor bug fixes to improve the stability of MI300 GPU applications. This release introduces several new driver features for system qualification on our partner server offerings. 
+
+### Library changes in ROCm 6.0.2
+
+| Library | Version |
+|---------|---------|
+| AMDMIGraphX |  ⇒ [2.8](https://github.com/ROCm/AMDMIGraphX/releases/tag/rocm-6.0.2) |
+| hipBLAS |  ⇒ [2.0.0](https://github.com/ROCm/hipBLAS/releases/tag/rocm-6.0.2) |
+| hipBLASLt |  ⇒ [0.6.0](https://github.com/ROCm/hipBLASLt/releases/tag/rocm-6.0.2) |
+| hipCUB |  ⇒ [3.0.0](https://github.com/ROCm/hipCUB/releases/tag/rocm-6.0.2) |
+| hipFFT |  ⇒ [1.0.13](https://github.com/ROCm/hipFFT/releases/tag/rocm-6.0.2) |
+| hipRAND |  ⇒ [2.10.17](https://github.com/ROCm/hipRAND/releases/tag/rocm-6.0.2) |
+| hipSOLVER |  ⇒ [2.0.0](https://github.com/ROCm/hipSOLVER/releases/tag/rocm-6.0.2) |
+| hipSPARSE |  ⇒ [3.0.0](https://github.com/ROCm/hipSPARSE/releases/tag/rocm-6.0.2) |
+| hipSPARSELt |  ⇒ [0.1.0](https://github.com/ROCm/hipSPARSELt/releases/tag/rocm-6.0.2) |
+| hipTensor |  ⇒ [1.1.0](https://github.com/ROCm/hipTensor/releases/tag/rocm-6.0.2) |
+| MIOpen |  ⇒ [2.19.0](https://github.com/ROCm/MIOpen/releases/tag/rocm-6.0.2) |
+| rccl |  ⇒ [2.15.5](https://github.com/ROCm/rccl/releases/tag/rocm-6.0.2) |
+| rocALUTION |  ⇒ [3.0.3](https://github.com/ROCm/rocALUTION/releases/tag/rocm-6.0.2) |
+| rocBLAS |  ⇒ [4.0.0](https://github.com/ROCm/rocBLAS/releases/tag/rocm-6.0.2) |
+| rocFFT |  ⇒ [1.0.25](https://github.com/ROCm/rocFFT/releases/tag/rocm-6.0.2) |
+| rocm-cmake |  ⇒ [0.11.0](https://github.com/ROCm/rocm-cmake/releases/tag/rocm-6.0.2) |
+| rocPRIM |  ⇒ [3.0.0](https://github.com/ROCm/rocPRIM/releases/tag/rocm-6.0.2) |
+| rocRAND |  ⇒ [3.0.0](https://github.com/ROCm/rocRAND/releases/tag/rocm-6.0.2) |
+| rocSOLVER |  ⇒ [3.24.0](https://github.com/ROCm/rocSOLVER/releases/tag/rocm-6.0.2) |
+| rocSPARSE |  ⇒ [3.0.2](https://github.com/ROCm/rocSPARSE/releases/tag/rocm-6.0.2) |
+| rocThrust |  ⇒ [3.0.0](https://github.com/ROCm/rocThrust/releases/tag/rocm-6.0.2) |
+| rocWMMA |  ⇒ [1.3.0](https://github.com/ROCm/rocWMMA/releases/tag/rocm-6.0.2) |
+| Tensile |  ⇒ [4.39.0](https://github.com/ROCm/Tensile/releases/tag/rocm-6.0.2) |
+
+#### hipFFT 1.0.13
+
+hipFFT 1.0.13 for ROCm 6.0.2
+
+##### Changes
+
+* Removed the Git submodule for shared files between rocFFT and hipFFT; instead, just copy the files
+ over (this should help simplify downstream builds and packaging)

default.xml

@@ -7,7 +7,7 @@
     <remote name="gpuopen-libs" fetch="https://github.com/GPUOpen-ProfessionalCompute-Libraries/" />
     <remote name="gpuopen-tools" fetch="https://github.com/GPUOpen-Tools/" />
     <remote name="KhronosGroup" fetch="https://github.com/KhronosGroup/" />
-    <default revision="refs/tags/rocm-6.0.0"
+    <default revision="refs/tags/rocm-6.0.2"
      remote="rocm-org"
      sync-c="true"
      sync-j="4" />
@@ -47,6 +47,7 @@
     <project groups="mathlibs" name="Tensile" />
     <project groups="mathlibs" name="hipTensor" />
     <project groups="mathlibs" name="hipBLAS" />
+    <project groups="mathlibs" name="hipBLASLt" />
     <project groups="mathlibs" name="rocFFT" />
     <project groups="mathlibs" name="hipFFT" />
     <project groups="mathlibs" name="rocRAND" />

docs/conceptual/More-about-how-ROCm-uses-PCIe-Atomics.rst

@@ -1,6 +1,6 @@
 .. meta::
    :description: How ROCm uses PCIe atomics
-   :keywords: PCIe, PCIe atomics, atomics, BAR memory
+   :keywords: PCIe, PCIe atomics, atomics, BAR memory, AMD, ROCm
 
 *****************************************************************************
 How ROCm uses PCIe atomics

docs/conceptual/ai-migraphx-optimization.md

@@ -2,7 +2,7 @@
   <meta charset="UTF-8">
   <meta name="description" content="Inference optimization with MIGraphX">
   <meta name="keywords" content="Inference optimization, MIGraphX, deep-learning, MIGraphX
-  installation">
+  installation, AMD, ROCm">
 </head>
 
 # Inference optimization with MIGraphX

docs/conceptual/ai-pytorch-inception.md

@@ -2,7 +2,7 @@
   <meta charset="UTF-8">
   <meta name="description" content="Inception V3 with PyTorch">
   <meta name="keywords" content="PyTorch, Inception V3, deep-learning, training data, optimization
-  algorithm">
+  algorithm, AMD, ROCm">
 </head>
 
 # Deep learning: Inception V3 with PyTorch

docs/conceptual/cmake-packages.rst

@@ -1,6 +1,6 @@
 .. meta::
    :description: Using CMake
-   :keywords: CMake, dependencies, HIP, C++
+   :keywords: CMake, dependencies, HIP, C++, AMD, ROCm
 
 *********************************
 Using CMake

docs/conceptual/compiler-disambiguation.md

@@ -1,7 +1,7 @@
 <head>
   <meta charset="UTF-8">
   <meta name="description" content="ROCm compilers disambiguation">
-  <meta name="keywords" content="compilers, compiler naming">
+  <meta name="keywords" content="compilers, compiler naming, AMD, ROCm">
 </head>
 
 # ROCm compilers disambiguation

docs/conceptual/file-reorg.md

@@ -1,7 +1,8 @@
 <head>
   <meta charset="UTF-8">
   <meta name="description" content="ROCm Linux Filesystem Hierarchy Standard reorganization">
-  <meta name="keywords" content="FHS, Linux Filesystem Hierarchy Standard, directory structure">
+  <meta name="keywords" content="FHS, Linux Filesystem Hierarchy Standard, directory structure,
+  AMD, ROCm">
 </head>
 
 # ROCm Linux Filesystem Hierarchy Standard reorganization

docs/conceptual/gpu-arch/mi100.md

@@ -1,7 +1,7 @@
 <head>
   <meta charset="UTF-8">
   <meta name="description" content="AMD Instinct MI100 microarchitecture">
-  <meta name="keywords" content="Instinct, MI100, microarchitecture">
+  <meta name="keywords" content="Instinct, MI100, microarchitecture, AMD, ROCm">
 </head>
 
 # AMD Instinct™ MI100 microarchitecture

docs/conceptual/gpu-arch/mi200-performance-counters.md

@@ -2,7 +2,7 @@
   <meta charset="UTF-8">
   <meta name="description" content="MI200 performance counters and metrics">
   <meta name="keywords" content="MI200, performance counters, counters, GRBM counters, GRBM,
-  CPF counters, CPF, CPC counters, CPC, command processor counters, SPI counters, SPI">
+  CPF counters, CPF, CPC counters, CPC, command processor counters, SPI counters, SPI, AMD, ROCm">
 </head>
 
 # MI200 performance counters and metrics

docs/conceptual/gpu-arch/mi250.md

@@ -1,7 +1,7 @@
 <head>
   <meta charset="UTF-8">
   <meta name="description" content="AMD Instinct MI250 microarchitecture">
-  <meta name="keywords" content="Instinct, MI250, microarchitecture">
+  <meta name="keywords" content="Instinct, MI250, microarchitecture, AMD, ROCm">
 </head>
 
 # AMD Instinct™ MI250 microarchitecture

docs/conceptual/gpu-isolation.md

@@ -2,7 +2,7 @@
   <meta charset="UTF-8">
   <meta name="description" content="GPU isolation techniques">
   <meta name="keywords" content="GPU isolation techniques, UUID, universally unique identifier,
-  environment variables, virtual machines">
+  environment variables, virtual machines, AMD, ROCm">
 </head>
 
 # GPU isolation techniques

docs/conceptual/gpu-memory.md

@@ -2,7 +2,7 @@
   <meta charset="UTF-8">
   <meta name="description" content="GPU memory">
   <meta name="keywords" content="GPU memory, VRAM, video random access memory, pageable
-  memory, pinned memory, managed memory">
+  memory, pinned memory, managed memory, AMD, ROCm">
 </head>
 
 # GPU memory
@@ -177,8 +177,8 @@ Fine-grained memory implies that up-to-date data may be made visible to others r
 
 | API                     | Flag                         | Coherence      |
 |-------------------------|------------------------------|----------------|
-| `hipExtMallocWithFlags` | `hipHostMallocDefault`       | Fine-grained   |
-| `hipExtMallocWithFlags` | `hipDeviceMallocFinegrained` | Coarse-grained |
+| `hipExtMallocWithFlags` | `hipDeviceMallocDefault`     | Coarse-grained |
+| `hipExtMallocWithFlags` | `hipDeviceMallocFinegrained` | Fine-grained   |
 
 | API                     | `hipMemAdvise` argument      | Coherence      |
 |-------------------------|------------------------------|----------------|

docs/conceptual/using-gpu-sanitizer.md

@@ -2,7 +2,7 @@
   <meta charset="UTF-8">
   <meta name="description" content="Using the LLVM ASan on a GPU">
   <meta name="keywords" content="LLVM, ASan, address sanitizer, AddressSanitizer, instrumented
-  libraries, instrumented applications">
+  libraries, instrumented applications, AMD, ROCm">
 </head>
 
 # Using the LLVM ASan on a GPU (beta release)

docs/conf.py

@@ -38,9 +38,9 @@ latex_elements = {
 # configurations for PDF output by Read the Docs
 project = "ROCm Documentation"
 author = "Advanced Micro Devices, Inc."
-copyright = "Copyright (c) 2023-2024 Advanced Micro Devices, Inc. All rights reserved."
-version = "6.0.0"
-release = "6.0.0"
+copyright = "Copyright (c) 2024 Advanced Micro Devices, Inc. All rights reserved."
+version = "6.0.1"
+release = "6.0.1"
 setting_all_article_info = True
 all_article_info_os = ["linux", "windows"]
 all_article_info_author = ""
@@ -50,7 +50,7 @@ article_pages = [
     {
         "file":"release",
         "os":["linux", "windows"],
-        "date":"2023-07-27"
+        "date":"2024-01-09"
     },
 
     {"file":"install/windows/install-quick", "os":["windows"]},

docs/contribute/building.md

@@ -1,7 +1,8 @@
 <head>
   <meta charset="UTF-8">
   <meta name="description" content="Building ROCm documentation">
-  <meta name="keywords" content="documentation, Visual Studio Code, GitHub, command line">
+  <meta name="keywords" content="documentation, Visual Studio Code, GitHub, command line,
+  AMD, ROCm">
 </head>
 
 # Building documentation

docs/contribute/feedback.md

@@ -1,7 +1,7 @@
 <head>
   <meta charset="UTF-8">
   <meta name="description" content="Providing feedback for ROCm documentation">
-  <meta name="keywords" content="documentation, pull request, GitHub">
+  <meta name="keywords" content="documentation, pull request, GitHub, AMD, ROCm">
 </head>
 
 # Providing feedback for ROCm documentation

docs/contribute/toolchain.md

@@ -1,7 +1,7 @@
 <head>
   <meta charset="UTF-8">
   <meta name="description" content="ROCm documentation toolchain">
-  <meta name="keywords" content="documentation, toolchain, Sphinx, Doxygen, MyST">
+  <meta name="keywords" content="documentation, toolchain, Sphinx, Doxygen, MyST, AMD, ROCm">
 </head>
 
 # ROCm documentation toolchain

docs/how-to/deep-learning-rocm.md

@@ -2,7 +2,7 @@
   <meta charset="UTF-8">
   <meta name="description" content="Deep learning using ROCm">
   <meta name="keywords" content="deep learning, frameworks, installation, PyTorch, TensorFlow,
-  MAGMA">
+  MAGMA, AMD, ROCm">
 </head>
 
 # Deep learning guide

docs/how-to/gpu-enabled-mpi.rst

@@ -1,3 +1,7 @@
+.. meta::
+   :description: GPU-enabled Message Passing Interface
+   :keywords: Message Passing Interface, MPI, AMD, ROCm
+
 ***************************************************************************************************
 GPU-enabled Message Passing Interface
 ***************************************************************************************************

docs/how-to/system-debugging.md

@@ -1,7 +1,8 @@
 <head>
   <meta charset="UTF-8">
   <meta name="description" content="System debugging guide">
-  <meta name="keywords" content="debug, system-level debug, debug flags, PCIe debug">
+  <meta name="keywords" content="debug, system-level debug, debug flags, PCIe debug, AMD,
+  ROCm">
 </head>
 
 # System debugging guide

docs/how-to/tuning-guides.md

@@ -2,7 +2,7 @@
   <meta charset="UTF-8">
   <meta name="description" content="Tuning guides">
   <meta name="keywords" content="high-performance computing, HPC, Instinct accelerators,
-  Radeon, tuning, tuning guide">
+  Radeon, tuning, tuning guide, AMD, ROCm">
 </head>
 
 # Tuning guides

docs/how-to/tuning-guides/mi100.md

@@ -2,7 +2,7 @@
   <meta charset="UTF-8">
   <meta name="description" content="MI100 high-performance computing and tuning guide">
   <meta name="keywords" content="MI100, high-performance computing, HPC, tuning, BIOS
-  settings, NBIO">
+  settings, NBIO, AMD, ROCm">
 </head>
 
 # MI100 high-performance computing and tuning guide

docs/how-to/tuning-guides/mi200.md

@@ -2,7 +2,7 @@
   <meta charset="UTF-8">
   <meta name="description" content="MI200 high-performance computing and tuning guide">
   <meta name="keywords" content="MI200, high-performance computing, HPC, tuning, BIOS
-  settings, NBIO">
+  settings, NBIO, AMD, ROCm">
 </head>
 
 # MI200 high-performance computing and tuning guide

docs/how-to/tuning-guides/w6000-v620.md

@@ -1,7 +1,8 @@
 <head>
   <meta charset="UTF-8">
   <meta name="description" content="RDNA2 workstation tuning guide">
-  <meta name="keywords" content="RDNA2, workstation tuning, BIOS settings, installation">
+  <meta name="keywords" content="RDNA2, workstation tuning, BIOS settings, installation, AMD,
+  ROCm">
 </head>
 
 # RDNA2 workstation tuning guide

docs/index.md

@@ -2,7 +2,7 @@
   <meta charset="UTF-8">
   <meta name="description" content="AMD ROCm documentation">
   <meta name="keywords" content="documentation, guides, installation, compatibility, support,
-  reference">
+  reference, ROCm, AMD">
 </head>
 
 # AMD ROCm™ documentation
@@ -13,6 +13,10 @@ resources to learn more about our products and what we support:
 * [What is ROCm?](./what-is-rocm.md)
 * [Release notes](./about/release-notes.md)
 
+You can install ROCm on our Radeon™, Radeon Pro™, and Instinct™ GPUs. If you're using Radeon
+GPUs, we recommend reading the
+{doc}`Radeon-specific ROCm documentation<radeon:index>`
+
 Our documentation is organized into the following categories:
 
 ::::{grid} 1 2 2 2
@@ -53,6 +57,7 @@ ROCm compatibility information
 * {doc}`User/kernel space<rocm-install-on-linux:reference/user-kernel-space-compat-matrix>`
 * {doc}`Docker<rocm-install-on-linux:reference/docker-image-support-matrix>`
 * [OpenMP](./about/compatibility/openmp.md)
+{doc}`ROCm on Radeon GPUs<radeon:index>`
 
 :::
 
@@ -100,7 +105,7 @@ Topic overviews & background information
 * [Compiler disambiguation](./conceptual/compiler-disambiguation.md)
 * [File structure (Linux FHS)](./conceptual/file-reorg.md)
 * [GPU isolation techniques](./conceptual/gpu-isolation.md)
-* [LLVN ASan](./conceptual/using-gpu-sanitizer.md)
+* [LLVM ASan](./conceptual/using-gpu-sanitizer.md)
 * [Using CMake](./conceptual/cmake-packages.rst)
 * [ROCm & PCIe atomics](./conceptual/More-about-how-ROCm-uses-PCIe-Atomics.rst)
 * [Inception v3 with PyTorch](./conceptual/ai-pytorch-inception.md)

docs/reference/library-index.md

@@ -3,7 +3,7 @@
   <meta name="description" content="ROCm API libraries & tools">
   <meta name="keywords" content="ROCm, API, libraries, tools, artificial intelligence, development,
   Communications, C++ primitives, Fast Fourier transforms, FFTs, random number generators, linear
-  algebra">
+  algebra, AMD">
 </head>
 
 # ROCm API libraries & tools

docs/reference/rocmcc.md

@@ -2,7 +2,7 @@
   <meta charset="UTF-8">
   <meta name="description" content="Compiler reference guide">
   <meta name="keywords" content="compiler, hipCC, Clang, amdclang, optimizations, LLVM,
-  rocm-llvm">
+  rocm-llvm, , AMD, ROCm">
 </head>
 
 # Compiler reference guide

docs/release/versions.md

@@ -1,10 +1,17 @@
+<head>
+  <meta charset="UTF-8">
+  <meta name="description" content="ROCm release history">
+  <meta name="keywords" content="documentation, release history, ROCm, AMD">
+</head>
+
 # ROCm release history
 
-| Version | Release Date |
+| Version | Release date |
 | ------- | ------------ |
 | [6.0.0](https://rocm.docs.amd.com/en/docs-6.0.0/) | Dec 15, 2023 |
 | [5.7.1](https://rocm.docs.amd.com/en/docs-5.7.1/) | Oct 13, 2023 |
 | [5.7.0](https://rocm.docs.amd.com/en/docs-5.7.0/) | Sep 15, 2023 |
+| [5.6.1](https://rocm.docs.amd.com/en/docs-5.6.1/) | Aug 29, 2023 |
 | [5.6.0](https://rocm.docs.amd.com/en/docs-5.6.0/) | Jun 28, 2023 |
 | [5.5.1](https://rocm.docs.amd.com/en/docs-5.5.1/) | May 24, 2023 |
 | [5.5.0](https://rocm.docs.amd.com/en/docs-5.5.0/) | May 1, 2023 |

docs/sphinx/_toc.yml.in

@@ -91,7 +91,7 @@ subtrees:
   - file: conceptual/gpu-isolation.md
     title: GPU isolation techniques
   - file: conceptual/using-gpu-sanitizer.md
-    title: LLVN ASan
+    title: LLVM ASan
   - file: conceptual/cmake-packages.rst
     title: Using CMake
   - file: conceptual/More-about-how-ROCm-uses-PCIe-Atomics.rst

docs/sphinx/requirements.in

@@ -1 +1 @@
-rocm-docs-core==0.30.3
+rocm-docs-core==0.33.0

docs/sphinx/requirements.txt

@@ -40,7 +40,7 @@ fastjsonschema==2.16.3
     # via rocm-docs-core
 gitdb==4.0.10
     # via gitpython
-gitpython==3.1.30
+gitpython==3.1.41
     # via rocm-docs-core
 idna==3.4
     # via requests
@@ -50,7 +50,7 @@ importlib-metadata==7.0.0
     # via sphinx
 importlib-resources==6.1.1
     # via rocm-docs-core
-jinja2==3.1.2
+jinja2==3.1.3
     # via
     #   myst-parser
     #   sphinx
@@ -100,7 +100,7 @@ requests==2.31.0
     # via
     #   pygithub
     #   sphinx
-rocm-docs-core==0.30.3
+rocm-docs-core==0.33.0
     # via -r requirements.in
 smmap==5.0.0
     # via gitdb

docs/what-is-rocm.md

@@ -1,7 +1,7 @@
 <head>
   <meta charset="UTF-8">
   <meta name="description" content="What is ROCm">
-  <meta name="keywords" content="documentation, projects, introduction">
+  <meta name="keywords" content="documentation, projects, introduction, ROCm, AMD">
 </head>
 
 # What is ROCm?
@@ -25,6 +25,11 @@ ROCm supports programming models, such as OpenMP and OpenCL, and includes all ne
 source software compilers, debuggers, and libraries. ROCm is fully integrated into machine learning
 (ML) frameworks, such as PyTorch and TensorFlow.
 
+```{tip}
+  If you're using Radeon GPUs, refer to the
+{doc}`Radeon-specific ROCm documentation<radeon:index>`
+```
+
 ## ROCm projects
 
 ROCm consists of the following drivers, development tools, and APIs.

tools/autotag/README.md

@@ -2,6 +2,7 @@
 
 ## Pre-requisites
 
+* Python 3.10
 * Create a GitHub Personal Access Token.
   * Tested with all the read-only permissions, but public_repo, read:project read:user, and repo:status should be enough.
   * Copy the token somewhere safe.
@@ -17,16 +18,16 @@
 * Run this for 5.6.0 (change for whatever version you require)
 * `GITHUB_ACCESS_TOKEN=my_token_here`
 
-To generate the changelog from 5.0.0 up to and including 5.7.1:
+To generate the changelog from 5.0.0 up to and including 6.0.1:
 
 ```sh
-python3 tag_script.py -t $GITHUB_ACCESS_TOKEN --no-release --no-pulls --do-previous --compile_file ../../CHANGELOG.md --branch release/rocm-rel-5.7 5.7.1
+python3 tag_script.py -t $GITHUB_ACCESS_TOKEN --no-release --no-pulls --do-previous --compile_file ../../CHANGELOG.md --branch release/rocm-rel-6.0 6.0.1
 ```
 
-To generate the changelog only for 5.7.1:
+To generate the changelog only for 6.0.1:
 
 ```sh
-python3 tag_script.py -t $GITHUB_ACCESS_TOKEN --no-release --no-pulls --compile_file ../../CHANGELOG.md --branch release/rocm-rel-5.7 5.7.1
+python3 tag_script.py -t $GITHUB_ACCESS_TOKEN --no-release --no-pulls --compile_file ../../CHANGELOG.md --branch release/rocm-rel-6.0 6.0.1
 ```
 
 ### Notes

tools/autotag/templates/rocm_changes/6.0.2.md

@@ -0,0 +1,10 @@
+The ROCm 6.0.2 point release consists of minor bug fixes to improve the stability of MI300 GPU applications. This release introduces several new driver features for system qualification on our partner server offerings. 
+
+#### hipFFT 1.0.13
+
+hipFFT 1.0.13 for ROCm 6.0.2
+
+##### Changes
+
+* Removed the Git submodule for shared files between rocFFT and hipFFT; instead, just copy the files
+ over (this should help simplify downstream builds and packaging)