-
Notifications
You must be signed in to change notification settings - Fork 13
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
Upgrade Kokkos 4.5.00 #144
Comments
@jacobmerson Do we care about maintaining support for Kokkos 4.4.00 and older that don't have the vendored mdspan enabled? I.e., can we require that Kokkos provides mdspan? If so, it will make the cmake and source code simpler. Specifically, the pcms vendored mdspan provides |
I don’t think we need to support old Kokkos. |
Here is my in-progress branch attempting to move to kokkos 4.5.01: https://github.com/SCOREC/pcms/tree/cws/kokkos45 Using
I think this may be a bug in the way kokkos installs these headers. The following uninformed hack to Kokkos 4.5.01 gets me past the above error, but results in several errors about
The first errors after the above kokkos hack are:
|
The namespace for |
This commit compiles with my hacked kokkos: d449f68 Some tests are failing:
Besides the smoke test, the failing tests require >=20 processes. Given that I'm running on a workstation, it seems somewhat reasonable that there are failures. @jacobmerson @Angelyr Is that correct? I'll dig into the failing smoke test. |
Here is the kokkos PR: kokkos/kokkos#7671 |
@jacobmerson Any thoughts on this kokkos/kokkos#7671 (review) ? I can think of three options:
|
I don’t remember using mdarray too many places. So I’d think it wouldn’t be too hard to remove. Please let me know if there are specific places that use it an we can come up with a plan to remove. |
OK. Here is the principle location: Lines 104 to 115 in 502999e
and grep reports (on my branch):
|
mdspan PR: kokkos/mdspan#376 |
Kokkos 4.4.00 and greater have mdspan built in which conflicts with the version we compile inside PCMS.
The text was updated successfully, but these errors were encountered: