Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Dynamically loaded HIP runtime library references incorrect version of hipDeviceGetProperties API #2728

Open
Rmalavally opened this issue Dec 15, 2023 · 0 comments
Open

Dynamically loaded HIP runtime library references incorrect version of hipDeviceGetProperties API #2728

Rmalavally opened this issue Dec 15, 2023 · 0 comments
Labels
6.0.0 Under Investigation Verified Issue AMD verified issue that is tracked for ROCm releases

Comments

@Rmalavally
Copy link
Contributor

When an application loads the HIP runtime library dynamically from ROCm 6.0 and attempts to use hipDeviceGetProperties, the application incorrectly uses the hipDeviceGetProperties API from a previous ROCm release instead of the newer ROCm 6.0 implementation.

The issue will be fixed in a future release.
@Rmalavally Rmalavally added 6.0.0 Under Investigation Verified Issue AMD verified issue that is tracked for ROCm releases labels Dec 15, 2023
@antiagainst antiagainst mentioned this issue Mar 4, 2024
Merged
antiagainst added a commit to iree-org/iree that referenced this issue Mar 4, 2024
@antiagainst
[hip][rocm] Fix hipGetDeviceProperties usage after ROCm 6.0 (#16643)
eda28bf 
ROCm 6.0 changes the `hipDeviceProp_t` struct, so we would need the new
`hipGetDevicePropertiesR0600()` API to query it--the existing
`hipGetDeviceProperties()`l API won't work for our case with dynamic
libraries.

Related to ROCm/ROCm#2728
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
6.0.0 Under Investigation Verified Issue AMD verified issue that is tracked for ROCm releases
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Rmalavally