Skip to content
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

Intel 2023 and MAPL 2.26 #3295

Open
lizziel opened this issue Jan 8, 2025 · 2 comments
Open

Intel 2023 and MAPL 2.26 #3295

lizziel opened this issue Jan 8, 2025 · 2 comments

Comments

@lizziel
Copy link
Contributor

lizziel commented Jan 8, 2025

I have a question from a GCHP user about the following compiler issue with Oneapi 23. Have you seen this? What are the Intel versions supported in MAPL 2.26?

-------------------------------------
[ 69%] Building Fortran object src/MAPL/generic/CMakeFiles/MAPL.generic.dir/BaseComponent.F90.o
/share/home/mxh/GCHP/src/MAPL/generic/BaseComponent.F90(17): error #6618: The INTERFACE/CONTAINS stack is full. This means that modules are being 'used' in a circular way.
contains
^
/share/home/mxh/GCHP/src/MAPL/generic/AbstractFrameworkComponent.F90(27): error #6618: The INTERFACE/CONTAINS stack is full. This means that modules are being 'used' in a circular way.
      end function i_AddChildComponent
^
compilation aborted for /share/home/mxh/GCHP/src/MAPL/generic/BaseComponent.F90 (code 1)
compilation aborted for /share/home/mxh/GCHP/src/MAPL/generic/AbstractFrameworkComponent.F90 (code 1)
make[2]: *** [src/MAPL/generic/CMakeFiles/MAPL.generic.dir/build.make:166: src/MAPL/generic/CMakeFiles/MAPL.generic.dir/BaseComponent.F90.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [src/MAPL/generic/CMakeFiles/MAPL.generic.dir/build.make:101: src/MAPL/generic/CMakeFiles/MAPL.generic.dir/AbstractFrameworkComponent.F90.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:4677: src/MAPL/generic/CMakeFiles/MAPL.generic.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
--------------------------------------------

Original issue at geoschem/GCHP#465.

@tclune
Copy link
Collaborator

tclune commented Jan 8, 2025

We have seen this before, though the details have escaped my memory. At best this is a misdiagnosis of an actual problem, but I think it is due to a compiler error.

@mathomp4 can list which Intel versions we currently test with.

@mathomp4
Copy link
Member

mathomp4 commented Jan 8, 2025

Well this is odd. I mean, I see in my notes I encountered this before, but I do not seem to have a solution noted. And those two files were a year or so old even at MAPL 2.26 time.

If this is 2023.1 that is ifort 2021.8 maybe? And that's a version we never tested with due to the OS update at NCCS (we had 2021.6 and 2021.7). Moreover, since MAPL 2.26 is from 2022, we never would have been able to.

I want to say 2023.2.1 was the first of the 2023 we tested with and that is ifort 2021.10. We do know that we had other bugs in GEOS that worked with 2021.6 and that 2021.10 fixed them.

Are you able to try a newer version of Intel ifort?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants