forked from abacusmodeling/abacus-develop
-
Notifications
You must be signed in to change notification settings - Fork 145
Closed
Labels
Compile & CICD & Docs & DependenciesIssues related to compiling ABACUSIssues related to compiling ABACUSGPU & DCU & HPCGPU and DCU and HPC related any issuesGPU and DCU and HPC related any issues
Description
Describe the bug
When compiling abacus with ROCM, errors are encounterd:
c++: error: unrecognized command line option ‘--offload-arch=gfx906’; did you mean ‘--offload-abi=ilp32’?And there are warnings about hipsolver
included in abacus-develop/source/module_base/module_container/base/macros/rocm.h:
In file included from /public/software/compiler/dtk/24.04.2/include/hipsolver/internal/hipsolver-types.h:20,
from /public/software/compiler/dtk/24.04.2/include/hipsolver/hipsolver.h:20,
from /work/home/abacus-develop/source/module_base/module_container/base/macros/rocm.h:7,
/public/software/compiler/dtk/24.04.2/include/hipblas.h:16:161: note: #pragma message: : warning : This file is deprecated. Use the header file from /opt/dtk-24.04.2/include/hipblas/hipblas.h by using #include <hipblas/hipblas.h>
#pragma message(": warning : This file is deprecated. Use the header file from /opt/dtk-24.04.2/include/hipblas/hipblas.h by using #include <hipblas/hipblas.h>")Expected behavior
Latest ABACUS should compile on this ROCM environment.
To Reproduce
No response
Environment
Environment
module list
Currently Loaded Modulefiles:
1) mpi/hpcx/2.12.0/gcc-8.3.1 2) compiler/dtk/24.04.2 3) compiler/cmake/3.23.3Compile & build
- Compiler: gcc-8.3.1
PACKAGES=/work/home/packages
cmake -B build -DBUILD_TESTING=ON -DCMAKE_INSTALL_PREFIX=~/.local/ \
-DUSE_OPENMP=ON -DENABLE_LCAO=OFF \
-DFFTW3_DIR=${PACKAGES}/fftw-3.3.10/build/ \
-DLAPACK_DIR=${PACKAGES}/OpenBLAS-0.3.28/build/lib \
-DSCALAPACK_DIR=${PACKAGES}/scalapack-2.2.0/ \
-DUSE_ROCM=ON
cmake --build build -j`nproc`Dependencies:
- fftw-3.3.10
- OpenBLAS-0.3.28
- scalapack-2.2.0
Additional Context
No response
Task list for Issue attackers (only for developers)
- Verify the issue is not a duplicate.
- Describe the bug.
- Steps to reproduce.
- Expected behavior.
- Error message.
- Environment details.
- Additional context.
- Assign a priority level (low, medium, high, urgent).
- Assign the issue to a team member.
- Label the issue with relevant tags.
- Identify possible related issues.
- Create a unit test or automated test to reproduce the bug (if applicable).
- Fix the bug.
- Test the fix.
- Update documentation (if necessary).
- Close the issue and inform the reporter (if applicable).
Metadata
Metadata
Assignees
Labels
Compile & CICD & Docs & DependenciesIssues related to compiling ABACUSIssues related to compiling ABACUSGPU & DCU & HPCGPU and DCU and HPC related any issuesGPU and DCU and HPC related any issues