github/ROCm
1
1
Fork 0
mirror of https://github.com/ROCm/ROCm.git synced 2026-01-10 23:28:03 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update RELEASE.md (#359)

Browse Source 
* Update RELEASE.md

added two new Resolved Issues and made two other changes

* Update RELEASE.md

Co-authored-by: Pratik Basyal <pratik.basyal@amd.com>

---------

Co-authored-by: Pratik Basyal <pratik.basyal@amd.com>
This commit is contained in:
randyh62
2025-04-02 10:26:50 -07:00
committed by GitHub
parent 600645d9eb
commit 7aa9f4dfb2
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
RELEASE.md
View File

@@ -762,10 +762,6 @@ and in-depth descriptions.
- Perl package installation is not required, and users will need to install this themselves if they want to.
- Support for ROCm Object tooling has moved into `llvm-objdump` provided by package `rocm-llvm`.
#### Removed
* HIP API `hipExtHostAlloc`.
#### Optimized
* `hipGraphLaunch` parallelism is improved for complex data-parallel graphs.
@@ -774,7 +770,9 @@ and in-depth descriptions.
#### Resolved issues
* Out-of-memory error on Microsoft Windows. When the user calls `hipMalloc` for device memory allocation while specifying a size larger than the available device memory, the HIP runtime fixes the error in the API implementation, allocating the available device memory plus system memory (shared virtual memory). This fix is not available on Linux.
* Out-of-memory error on Microsoft Windows. When the user calls `hipMalloc` for device memory allocation while specifying a size larger than the available device memory, the HIP runtime fixes the error in the API implementation, allocating the available device memory plus system memory (shared virtual memory).
* Error of dependency on libgcc-s1 during rocm-dev install on Debian Buster. HIP runtime now uses libgcc1 for this distros.
* Stack corruption during kernel execution. HIP runtime now adds a maximum stack size limit based on the GPU device feature.
#### Upcoming changes