-
Notifications
You must be signed in to change notification settings - Fork 26
Problems building apex with ROCm-5.4, 5.5, and 5.6 #115
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
Comments
I'm seeing this as well, a number of errors like those above while building the cuda_ext.
|
FYI @jithunnair-amd |
Hi @adammoody and @loadams, if you are using PyTorch 2.0 or earlier, please use master branch for apex. If you are using PyTorch 2.1+, please use torch_2.1_higher branch. There are some changes related to CUDA to HIP conversion in PyTorch. export HIP_PLATFORM_HCC I am not apex developer. |
Hi @adammoody. Do you still need assistance with this ticket? If not, please close the ticket. Thanks! |
Describe the Bug
The latest
master
branch fails to build with several ROCm versions, including 5.4, 5.5, and 5.6.Rolling back to the commit made on June 20 (
git checkout 10c7482
) allows ROCm-5.4 to build. The build still fails for 5.5 and 5.6 but with a different error.Minimal Steps/Code to Reproduce the Bug
For ROCm-5.4.3, I use the following to build:
The build fails when compiling
csrc/mlp_hip.hip
with errors like the following:Rolling back to the commit from June 20 allows the build to complete:
Building apex from
master
with ROCm-5.5 and ROCm-5.6 fail with errors similar to each other, but errors that are distinct from ROCm-5.4. Here are the steps I used to build with ROCm-5.6:That fails with the following error:
In this case, rolling back to the June 20 commit fails with a different error:
Building with the June 20 commit, I see that the
csrc/mlp_hip.hip
file contains the following for ROCm-5.5 and ROCm-5.6 (which fails):but it has the following for ROCm-5.4 (which builds):
Expected Behavior
Environment
The text was updated successfully, but these errors were encountered: