Update EKAT in E3SM#8386
Merged
tcclevenger merged 2 commits intoMay 13, 2026
Merged
Conversation
Contributor
Author
|
Waiting for fix in E3SM-Project/EKAT#443 |
Changes: - Expressions API rework - Managed memory alias
This is clearer than Kokkos::MemoryTraits<0>
tcclevenger
force-pushed
the
tcclevenger/update_ekat
branch
from
6746774 to
7394509
Compare
Contributor
Author
Done |
bartgol
approved these changes
May 13, 2026
tcclevenger
added a commit
that referenced
this pull request
May 13, 2026
I'm doing this to prep for updating to C++20 and then Kokkos 5. I don't want any additional ekat changes included when doing that ekat update since nightly testing on all machines will be important (and I don't want errors coming from other places). [BFB]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm doing this to prep for updating to C++20 and then Kokkos 5. I don't want any additional ekat changes included when doing that ekat update since nightly testing on all machines will be important (and I don't want errors coming from other places).
[BFB]