Closed bartlettroscoe closed 6 years ago
@ibaned, do you mind if I merge this change to nvcc_wrapper
directly into Trilinos in a Trilinos PR? As long as nvcc_wrapper
gets updated in kokkos
before the next time that kokkos
gets updated into Trilinos, then this change will not get overwritten. (That is what is nice about the snapshotting model. It eliminates merge conflicts but you have to be careful you don't overwrite changes that you want to keep.) But if it did get overwritten temporarily, that would not be a big deal because this debug option is not being used in any production setting.
@bartlettroscoe just go ahead and do it. We will merge this into Kokkos develop too.
Note you will get a number of other updates to nvcc_wrapper though. You may wanna check that the CUDA build is working.
@crtrott write:
Note you will get a number of other updates to nvcc_wrapper though. You may wanna check that the CUDA build is working.
In the Trilinos branch, I actually only added just these print statements. It is not the version of nvcc-wrapper
that is one this develop
branch.
This allows you to see the actually nvcc commands that are run by the nvcc_wrapper while it is running. This is very useful for debugging problems with the nvcc_wrapper script and problem with nvcc itself.
I needed this to help debug issues with resoruce file handling with Ninja for trilinos/Trilinos#3069.