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.

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

HIP rocm-4.5.x install from source on NVIDIA platform #2413

Closed
jakub-homola opened this issue Nov 9, 2021 · 1 comment · May be fixed by ROCm/hipamd#9
Closed

HIP rocm-4.5.x install from source on NVIDIA platform #2413

jakub-homola opened this issue Nov 9, 2021 · 1 comment · May be fixed by ROCm/hipamd#9

Comments

@jakub-homola
Copy link

If I understand correctly, with the new rocm-4.5.x branches, this HIP repository contains only several things common to both NVIDIA and AMD platforms. Then there is the hipamd repository, which "provides HIP implementation specifically for AMD platform", according to the readme. I did not find anything about hipnvidia or anything like that.

The INSTALL.md seems to be relevant only for the AMD platform, since it mentions ROC* requirements, which are required only on the AMD platform.

So, what is currently the correct way of installing HIP from source on the NVIDIA platform?

I tried using only HIP as in previous versions, but hipcc complains about <hip/hip_version.h> not found, which really isn't there. Also the *_detail include directories are missing.

hipamd does work on the NVIDIA platform, but it seems weird, since it is supposed to be designed specifically for AMD.

@jakub-homola jakub-homola changed the title HIP 4.5.x install from source on NVIDIA HIP rocm-4.5.x install from source on NVIDIA platform Nov 9, 2021
@ppanchad-amd
Copy link

@jakub-homola Apologies for the lack of response. Can you please test with latest ROCm 6.0.2 (HIP 6.0.32831)? If resolved, please close ticket. Thanks!

@ppanchad-amd ppanchad-amd closed this as not planned Won't fix, can't repro, duplicate, stale Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants