-
Notifications
You must be signed in to change notification settings - Fork 765
{tools}[GCCcore/14.2.0] ROCm-LLVM v19.0.0 w/ ROCm 6.4.1 #23304
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
base: develop
Are you sure you want to change the base?
{tools}[GCCcore/14.2.0] ROCm-LLVM v19.0.0 w/ ROCm 6.4.1 #23304
Conversation
…Cm-LLVM-6.4.1_llvm-project-19.0.0_fix-offload-build.patch Co-Authored-By: Bob Dröge <[email protected]>
2bf841b to
7c46968
Compare
|
MI250X node with Test report by @Thyre |
|
@boegelbot please test @ jsc-zen3 |
|
@Thyre: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... - notification for comment with ID 3126806295 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
MI100+MI210 node with Test report by @bedroge |
Signed-off-by: Jan André Reuter <[email protected]>
…asyconfigs into 20250703205604_new_pr_ROCm-LLVM641
Signed-off-by: Jan André Reuter <[email protected]>
|
@boegelbot please test @ jsc-zen3 |
|
@Thyre: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... - notification for comment with ID 3444812706 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
Signed-off-by: Jan André Reuter <[email protected]>
|
@boegelbot please test @ jsc-zen3 |
|
@Thyre: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... - notification for comment with ID 3444883950 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
easybuild/easyconfigs/r/ROCm-LLVM/ROCm-LLVM-19.0.0-GCCcore-14.2.0-ROCm-6.4.1.eb
Outdated
Show resolved
Hide resolved
easybuild/easyconfigs/r/ROCm-LLVM/ROCm-LLVM-19.0.0-GCCcore-14.2.0-ROCm-6.4.1.eb
Outdated
Show resolved
Hide resolved
…2.0-ROCm-6.4.1.eb Co-authored-by: Bob Dröge <[email protected]>
…2.0-ROCm-6.4.1.eb Co-authored-by: Bob Dröge <[email protected]>
|
Forgot Test report by @Thyre |
|
Test report by @Thyre |
|
@boegelbot please test @ jsc-zen3 |
|
@Thyre: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... - notification for comment with ID 3447807268 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
Hm, we already have The module is looking entirely fine, and trying to manually link a similar program with |
|
@boegelbot please test @ jsc-zen3 |
|
@Thyre: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... - notification for comment with ID 3448276629 processed Message to humans: this is just bookkeeping information for me, |
|
The test build on my machine got stuck, there seems to be an issue with the GPU (even |
|
Test report by @boegelbot |
|
Test report by @bedroge |
Exactly the same failure... I guess we need to do a "manual" build on |
(created using
eb --new-pr)Requires:
amdgcn-capabilitiesconfiguration option andamdgcn_capabilitieseasyconfig parameter + related templates, similar tocuda-compute-capabilitieseasybuild-framework#4860amdgcn_capabilitiesbuild option easybuild-easyblocks#3824This is the first major step towards building ROCm and it's components. ROCm-LLVM is a fork of upstream LLVM with several major additions. This complicates the build process a lot, e.g. requiring to basically build ROCm-LLVM twice just to get some offload components working correctly.
Most of the heavy lifting was done by @bedroge, most of my work was just to bring this to GCCcore/14.2.0, figure out build issues and adding the patch to get the OpenMP Tools Interface working.
We skip building and running tests, as the build already takes ages.
One important difference to "upstream" (i.e. AMD's fork) is that we build
amdflangfrom LLVM. We therefore choose to adopt the newflangearlier than AMD does for their official packages. I don't see a reason to still try to go with the oldflang.