Rocm 5.2 release integration#31591
Conversation
|
Installed all component successfully. Unit test result in hip below. rocm-bandwidth-test result below. |
cgmb
left a comment
There was a problem hiding this comment.
There's just one more thing in the rocblas package that I see.
24c5ab0
1775f9b
|
@haampie , @tldahlgren can you approve this PR and let us know if this can be merged |
|
@haampie or @tldahlgren can you approve this PR. i am planning to get 5.2.1 after this PR merge. |
70373ac
|
@alalazo or @tldahlgren can we get this merged now |
alalazo
left a comment
There was a problem hiding this comment.
I did a first pass at reading the PR. I didn't comment on each place since I think there would be a lot of repetitions in my comments. Basically:
- There are a lot of patches that I'd really like to see moving upstream
- The patch directives usually don't have comments to explain what they do, who produced the patch etc.
- The patches themselves don't have provenance
This wouldn't make life easy for whomever reads these package.py next. Can we handle these issues?
Note that I didn't comment on functional changes, since I don't know much about the rocm stack, so I'll defer that to other maintainers/core-developers.
| args.append("-DGINKGO_HIP_AMDGPU={0}".format(arch_str)) | ||
| if spec.satisfies("^[email protected]:"): | ||
| args.append( | ||
| "-DCMAKE_MODULE_PATH={0}/".format(self.spec["hip"].prefix.lib.cmake.hip) |
There was a problem hiding this comment.
Removed the / in the recipe.
| when="@5.0.2:5.1.3", | ||
| ) | ||
|
|
||
| patch( | ||
| "0012-Improve-compilation-without-git-repo-and-remove-compiler-rt-linkage-for-host" | ||
| ".5.2.0.patch", | ||
| when="@5.2.0:", |
There was a problem hiding this comment.
Same comments as above:
- It would be better is this is fixed upstream
- In any case a comment explaining what the patch does, why is it needed and where it was taken from is welcome to help the next reader of
package.py
There was a problem hiding this comment.
@alalazo I have been working with the team to get this changes into the next release . While 5.2.1 will not have this change, i would see that this is addressed in 5.3.0 release.
There was a problem hiding this comment.
The compilation without git was fixed in ROCm/hipamd@56b3260 and is on track for ROCm 5.3. If you have a fix for the rt linkage, that's great!
the new patches applied in rocm components
|
Hi @alalazo , |
alalazo
left a comment
There was a problem hiding this comment.
Changing the maintainers and adding tags can be extracted to a separate PR. I think that wouldn't require a lot of reviews to be merged. There are other comments below, always related to patches.
If I understand correctly this package is maintained by AMD people. May I ask why AMD is releasing versions of the Rocm stack that are then heavily patched afterwards in Spack?
| url = "https://github.com/RadeonOpenCompute/ROC-smi/archive/rocm-4.1.0.tar.gz" | ||
|
|
||
| maintainers = ["srekolam", "arjun-raj-kuppala"] | ||
| maintainers = ["srekolam", "renjithravindrankannath"] |
There was a problem hiding this comment.
Change in maintainers and tags can be a separate PR.
haampie
left a comment
There was a problem hiding this comment.
Just a few comments:
1.Please use define(var, val) and for ON/OFF you can use Python's booleans so that you get -Dvar:BOOL=val.
2. If you wanna change the behavior at 5.2.0, then use @:5.1 for < 5.2.0 and @5.2.0: for >= 5.2.0 so there's no possible versions between 5.1.3 - 5.2.0 (which guards against someone adding a 5.1.3-my-custom-version suffix or so).
This PR contains changes for ROCM 5.2.0 release.
Additional changes for hipify-clang and rocm-openmp-extras will be under different PR