-
Notifications
You must be signed in to change notification settings - Fork 406
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
Deprecate finalize_all()
#5134
Deprecate finalize_all()
#5134
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this mean that this functionality is not needed or is this already being done in the regular finalize
?
core/src/impl/Kokkos_Core.cpp
Outdated
@@ -995,10 +995,12 @@ void push_finalize_hook(std::function<void()> f) { finalize_hooks.push(f); } | |||
|
|||
void finalize() { Impl::finalize_internal(); } | |||
|
|||
void finalize_all() { | |||
#ifdef KOKKOS_ENABLE_DEPRECATED_CODE_3 | |||
KOKKOS_DEPRECATED void finalize_all() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is to be deprecated, should Impl::finalize_internal
also be refactored to not have a default argument? Currently, it seems to be only called from finalize
and finalize_all
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I pretty much have the same question. What functionality do we need to offer to initialize and finalize individual backends? What are we promising to, say, Legion
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dropped the boolean argument from Implemented::finalize()
.
Cleaning further raises a few questions
kokkos/core/src/impl/Kokkos_Core.cpp
Lines 123 to 127 in 7a413b5
void ExecSpaceManager::finalize_spaces(const bool all_spaces) { | |
for (auto& to_finalize : exec_space_factory_list) { | |
to_finalize.second->finalize(all_spaces); | |
} | |
} |
virtual void finalize(const bool all_spaces) = 0; |
Presumably they are space we don't know about that inherits from
ExecSpaceInitializerBase
so we need to be careful there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO, it's fair to also drop it from
void ExecSpaceManager::finalize_spaces(const bool all_spaces)
since we control that as well but I agree to be careful about going deeper.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Failures (one of the machine out of disk space) are unrelated. This is ready for merge. |
Compatibility update for disable of kokkos deprecated code Necessary for kokkos@4.0 release, see kokkos/kokkos#5134
Compatibility update for disable of kokkos deprecated code Necessary for kokkos@4.0 release, see kokkos/kokkos#5134
Oversight on our part, not used and not tested