@hkvzjal it looks like cross language inlining is not supported. I don’t know if that is what they needed. It goes back to my comment here: An evaluation of risks associated with relying on Fortran for mission critical codes for the next 15 years - #4 by certik, where I suggest that mixing of languages generally makes everything worse, you have all these interface problems. It’s better to choose just one language and do things in it. This is a tough problem, since they are using Amrex, which is in C++, and it might be hard to create performing Fortran wrappers so that one can use it with Fortran projects and run well on GPUs. I think long term there should be a way to do that, but I can easily see how this becomes a maintenance burden, and just doing it in C++ is a lot simpler.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
An evaluation of risks associated with relying on Fortran for mission critical codes for the next 15 years
|
82 | 7164 | July 2, 2023 | |
Parallel Fortran Coarrays Longer CPU Time Than Serial Fortran
|
18 | 483 | November 4, 2024 | |
Virtual Tutorial: Introduction to HPC with Chapel, UPC++ and Coarray Fortran | 1 | 589 | July 25, 2023 | |
Questions from a Fortran HPC Webinar | 30 | 2658 | July 15, 2021 | |
Parallel programming resources
|
2 | 587 | October 14, 2021 |