-
Notifications
You must be signed in to change notification settings - Fork 407
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
Create Kokkos Bill of Materials #632
Comments
YES! I want to add this type of functionality to Trilinos. If you have work with Petsc, anytime something goes completely wrong, it prints a stack trace (if you compiled with their debug flag). It also shows the exact line used to ./configure the build. I want this information for performance tracking: Which TPLs (blas/lapack) were used and which version. The compiler used and its version. I think it will be extremely value when providing user support as well. (not related to Kokkos, just an FYI) You may want to consider how Petsc has used this type of functionality in conjunction with bad things happening. E.g., if you reach a bad state, this info becomes part of the exception handler so the user has something useful to bring to a github issue. |
It's not hard for us to tie this into TEUCHOS_TEST_EXCEPTION* macros, or make it an MPI_Finalize or atexit hook. |
Output from Kokkos::print_configuration( out, false ) Compiler: Runtime Configuration: |
Create Kokkos::print_configuration which will dump all configuration and runtime parameters
The text was updated successfully, but these errors were encountered: