Update RELEASE.md (#581)

* Update RELEASE.md

Remove support for rocBlas and hipBlasLt

* Update CHANGELOG.md

Removed from the Changelog as well.
This commit is contained in:
randyh62
2025-10-09 13:15:08 -07:00
committed by GitHub
parent 978c58d196
commit c06242bb89
2 changed files with 1 additions and 3 deletions

View File

@@ -42,7 +42,6 @@ for a complete overview of this release.
#### Added #### Added
* Support for rocBLAS and hipBLASLt targeting gfx1150 and gfx1151.
* Support for the `hipMemAllocationTypeUncached` flag, enabling developers to allocate uncached memory. This flag is now supported in the following APIs: * Support for the `hipMemAllocationTypeUncached` flag, enabling developers to allocate uncached memory. This flag is now supported in the following APIs:
- `hipMemGetAllocationGranularity` determines the recommended allocation granularity for uncached memory. - `hipMemGetAllocationGranularity` determines the recommended allocation granularity for uncached memory.
- `hipMemCreate` allocates memory with uncached properties. - `hipMemCreate` allocates memory with uncached properties.

View File

@@ -615,7 +615,6 @@ For a historical overview of ROCm component updates, see the {doc}`ROCm consolid
#### Added #### Added
* Support for rocBLAS and hipBLASLt targeting gfx1150 and gfx1151.
* Support for the `hipMemAllocationTypeUncached` flag, enabling developers to allocate uncached memory. This flag is now supported in the following APIs: * Support for the `hipMemAllocationTypeUncached` flag, enabling developers to allocate uncached memory. This flag is now supported in the following APIs:
- `hipMemGetAllocationGranularity` determines the recommended allocation granularity for uncached memory. - `hipMemGetAllocationGranularity` determines the recommended allocation granularity for uncached memory.
- `hipMemCreate` allocates memory with uncached properties. - `hipMemCreate` allocates memory with uncached properties.
@@ -776,4 +775,4 @@ clang-offload-bundles into individual code objects found within the objects
or executables passed as input. The ``llvm-objdump --offloading`` tool option also or executables passed as input. The ``llvm-objdump --offloading`` tool option also
supports the ``--arch-name`` option, and only extracts code objects found with supports the ``--arch-name`` option, and only extracts code objects found with
the specified target architecture. See [llvm-objdump](https://llvm.org/docs/CommandGuide/llvm-objdump.html) the specified target architecture. See [llvm-objdump](https://llvm.org/docs/CommandGuide/llvm-objdump.html)
for more information. for more information.