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

Support for Intel 2022 #82

Open
lizziel opened this issue Sep 27, 2024 · 4 comments
Open

Support for Intel 2022 #82

lizziel opened this issue Sep 27, 2024 · 4 comments
Assignees

Comments

@lizziel
Copy link

lizziel commented Sep 27, 2024

I am running into the issue below when running with Intel2022.2.1. I see only 2021 is listed as supported Intel compiler but I wonder how much effort it would be to extend that to 2022?

forrtl: severe (408): fort: (7): Attempt to use pointer THIS when it is not associated with a target

Image              PC                Routine            Line        Source
gchp               000000000207266F  fy_stringnodemap_         408  procedures.inc
gchp               000000000355852A  Unknown               Unknown  Unknown
gchp               00000000035594E3  Unknown               Unknown  Unknown
gchp               00000000020796E9  fy_parser_mp_new_         101  Parser.F90
gchp               0000000001FC972B  Unknown               Unknown  Unknown
gchp               0000000001C5E260  Unknown               Unknown  Unknown
gchp               0000000001C5E5F6  Unknown               Unknown  Unknown
gchp               0000000000F9B458  Unknown               Unknown  Unknown
gchp               000000000042D7B8  MAIN__                     28  GCHPctm.F90
gchp               000000000042BE1D  Unknown               Unknown  Unknown
libc.so.6          00001495C1A00EB0  Unknown               Unknown  Unknown
libc.so.6          00001495C1A00F60  __libc_start_main     Unknown  Unknown
gchp               000000000042BD35  Unknown               Unknown  Unknown
@mathomp4
Copy link
Collaborator

Huh. I mean, we run this with Intel ifort 2021.13 which is from 2024.2.0. So I'm wondering if this is a compiler bug...

That said, what version of MAPL are you using? Technically, nothing in MAPL relies on yaFyaml anymore since we moved to use ESMF_Hconfig.

@lizziel
Copy link
Author

lizziel commented Oct 4, 2024

Interesting, I didn't realize yafyaml was retired. I am using a very old version of MAPL, 2.26, with no plans to update until MAPL3. I'll see if the sysadmins of the cluster can add Intel 2021.13 support.

@tclune
Copy link
Member

tclune commented Oct 4, 2024

Interesting, I didn't realize yafyaml was retired. I am using a very old version of MAPL, 2.26, with no plans to update until MAPL3. I'll see if the sysadmins of the cluster can add Intel 2021.13 support.

Well, MAPL still depends on pFlogger which depends on yaFyaml. So yaFyaml is not retired. I would like to make an option in pFlogger to rely on ESMF yaml (hconfig), but that is a rainy day item.

@mathomp4
Copy link
Collaborator

mathomp4 commented Oct 4, 2024

Interesting, I didn't realize yafyaml was retired. I am using a very old version of MAPL, 2.26, with no plans to update until MAPL3. I'll see if the sysadmins of the cluster can add Intel 2021.13 support.

Well, MAPL still depends on pFlogger which depends on yaFyaml. So yaFyaml is not retired. I would like to make an option in pFlogger to rely on ESMF yaml (hconfig), but that is a rainy day item.

Ohh. Whoops. I didn't realize that. Or rather, I forgot that. I guess there isn't an explicit dependency on yafyaml anymore. But there is a dependency if you want pFlogger support.

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