Initialize and Finalize

Kokkos::initialize

Initializes Kokkos internal objects and all enabled Kokkos backends.

See Kokkos::initialize for details.

Kokkos::finalize

Shutdown Kokkos initialized execution spaces and release internally managed resources.

See Kokkos::finalize for details.

Kokkos::is_initialized

Allows to query initialization status of Kokkos and returns true if Kokkos is initialized.

See Kokkos::is_initialized for details.

Kokkos::is_finalized

Allows to query finalizaton status of Kokkos and returns true is Kokkos is finalized.

See Kokkos::is_finalized for details.

Kokkos::ScopeGuard

Kokkos::ScopeGuard is a class which aggregates the resources managed by Kokkos. ScopeGuard will call Kokkos::initialize when constructed and Kokkos::finalize when destructed, thus the Kokkos context is automatically managed via the scope of the ScopeGuard object.

See Kokkos::ScopeGuard for details.

ScopeGuard aids in the following common mistake which is allowing Kokkos objects to live past Kokkos::finalize:

int main(int argc, char** argv) {
  Kokkos::initialize(argc, argv);
  Kokkos::View<double*> my_view("my_view", 10);
  Kokkos::finalize();
  // my_view destructor called after Kokkos::finalize !
}

Switching to Kokkos::ScopeGuard fixes it:

int main(int argc, char** argv) {
  Kokkos::ScopeGuard kokkos(argc, argv);
  Kokkos::View<double*> my_view("my_view", 10);
  // my_view destructor called before Kokkos::finalize
  // ScopeGuard destructor called, calls Kokkos::finalize
}

In the above example, my_view will not go out of scope until the end of the main() function. Without ScopeGuard, Kokkos::finalize will be called before my_view is out of scope. With ScopeGuard, ScopeGuard will be dereferenced (subsequently calling Kokkos::finalize) after my_view is dereferenced, which ensures the proper order during shutdown.