CI: AMD hip::device also for Fortran#2595
CI: AMD hip::device also for Fortran#2595WeiqunZhang merged 2 commits intoAMReX-Codes:developmentfrom
hip::device also for Fortran#2595Conversation
By now (HIP 4.5), we should be able to link also against Fortran targets.
3c54722 to
72ad01f
Compare
hip::device also for Fortranhip::device also for Fortran
|
Tested on OLCF Crusher with this environment: https://warpx.readthedocs.io/en/latest/install/hpc/crusher.html |
|
If I add again Cray CC compilation on Crusher with ROCm 4.5.2:
Originally, I just extracted them from |
| # note: already bumped to C++17 (cxx_std_17) or newer in AMReX_Config.cmake | ||
|
|
||
| # work-around for ROCm <=4.2 | ||
| # https://github.com/ROCm-Developer-Tools/HIP/pull/2190 |
Does not harm to add them unconditionally again.
|
Added the flags unconditionally now so that HPE/Cray |
hip::device also for Fortranhip::device also for Fortran
|
@WeiqunZhang I renamed the |
Summary
By now (HIP 4.5), we should be able to link also against Fortran targets.
Let's remove work-arounds and ditch old HIP releases, so improve maintainability and avoid surprises.
Additional background
X-ref:
Checklist
The proposed changes: