-
Notifications
You must be signed in to change notification settings - Fork 10
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
Build with rocm/5.6 on Frontier (~ginkgo) #89
Conversation
…s (e.g., hipblas/hipblas.h), which generates a preprocessor errors in rocm 5.6, causing an ExaGO build failure in Debug mode. See https://rocm.docs.amd.com/en/docs-5.6.0/CHANGELOG.html#id31 and https://bitbucket.org/icl/magma/commits/f07ddb12ca3f3aad9253342b6800e48bd8f02888.
Currently seeing some test failures I hadn't seen before. I wonder if it is due to the rocm/5.6 upgrade or something else. I will investigate.
|
On the failing tests:
Test 20 log on Frontier
Test 2 backtrace
I can upgrade to hiop@develop and see what happens. |
Closing this PR:
|
Merge request type
Relates to
This MR updates
Summary
This MR updates the Spack configuration and the corresponding modules on Frontier to build with rocm/5.6.
A few notes:
x86-64
target instead ofzen3
because of a compiler bug raised by PETSc (see Spack environment with ROCm 5.6 fails to build PETSc #65). I opened an OLCF ticket to address this.zen3
, so the path to the modules files was not correctly updated by default. I manually modified it, and I welcome suggestions for a sustainable solution.Debug
mode against [email protected], which was using the old paths. [email protected]+ implements a logic to ensure the correct paths are used depending on the ROCm version (see https://bitbucket.org/icl/magma/commits/f07ddb12ca3f3aad9253342b6800e48bd8f02888). The current build on Frontier relies on [email protected].