Merge ~tchavadar/ubuntu/+source/pkg-rocm-tools:ubuntu/devel into ubuntu/+source/pkg-rocm-tools:ubuntu/devel
Proposed by
Talha Can Havadar
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Merge reported by: | Talha Can Havadar | ||||
| Merged at revision: | 42fb03b58d21cf6eddb863e79a524b4a25eed271 | ||||
| Proposed branch: | ~tchavadar/ubuntu/+source/pkg-rocm-tools:ubuntu/devel | ||||
| Merge into: | ubuntu/+source/pkg-rocm-tools:ubuntu/devel | ||||
| Diff against target: |
104 lines (+40/-14) 3 files modified
bin/rocm-target-arch (+24/-14) data/build-targets/resolute (+1/-0) debian/changelog (+15/-0) |
||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Frank Heimes (community) | Approve | ||
| git-ubuntu import | Pending | ||
|
Review via email:
|
|||
Description of the change
Adding gfx11-generic to build targets enables ROCm stack to build for other platforms.
I have AMD Ryzen AI 7 350 cpu which has gfx1152 together with it. This would allow those PCs to utilize ROCm as well.
That said, option introduced to llvm with this commit: https:/
I am still thinking if we should use gfx1152 and gfx1153 directly instead of gfx11-generic but not exactly sure about the performance benefits of optimized builds but the generic would at least enable the platform so thats why I created this merge proposal.
To post a comment you must log in.

So this is supposed to be a new version that should bump the existing version in resolute,
means replacing the currently existing 0.9.4ubuntu1. With that the new version (0.9.5ubuntu1) is fine.
I think that the modifications are reasonable and pretty straight forward - nevertheless I always recommend to do a test build in PPA (not sure if ouy've done that, if so just reference it here and/or in the associated LP bug, since it always increases confidence).
However, I cannot elaborate on your thought "if we should use gfx1152 and gfx1153 directly instead of gfx11-generic", but using gfx11-generic does not seem to be a bad thing.
Only issue I see is the changelog, that requires a reference to the LP bug number.
And if there is no LP bug yet, once is needed just for this (but since it's an update in Ubuntu devel, the entire SRU template is not needed.)
So needs minor fixing ...