-
Notifications
You must be signed in to change notification settings - Fork 99
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
PortableNumericCHASH can't align shared memory #587
Comments
@crtrott yes, that was added after dealing with the shmem alignment issues. the requested shmem from the handle probably needs to be adjusted. |
Original issue #500 |
Have a better handle on this, issues are occurring when dealing ensemble-like types. Reverting this changes from #500 to determine |
Address issue #587 Integration testing with Trilinos exposed issues with handling of shmem alignment with ensemble types. This PR: 1. reverts how thread_memory is computed during functor construction 2. removes throws within functors when shmem unaligned 3. adds warning message and throws prior to kernel launch for cases with inappropriate shmem sizes 4. guards shmem realignment with KOKKOS_ENABLE_COMPLEX_ALIGN this keeps behavior consistent with Trilinos, but will need to be further addressed 5. some formatting cleanup and comments added
Address issue #587 Integration testing with Trilinos exposed issues with handling of shmem alignment with ensemble types. This PR: 1. reverts how thread_memory is computed during functor construction 2. removes throws within functors when shmem unaligned 3. adds warning message and throws prior to kernel launch for cases with inappropriate shmem sizes 4. guards shmem realignment with KOKKOS_ENABLE_COMPLEX_ALIGN this keeps behavior consistent with Trilinos, but will need to be further addressed 5. some formatting cleanup and comments added
This makes the PR for Kokkos/KokkosKernels Integration fail right now.
https://testing.sandia.gov/cdash/testDetails.php?test=100331563&build=6287299
This fails here:
KokkosSparse_spgemm_impl_kkmem.hpp:204
The text was updated successfully, but these errors were encountered: