Skip to content
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.

Sign up for GitHub

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

Jump to bottom

BUG: Call SetGlobalDefaultNumberOfThreads when processing "-threads" #1195

Merged
merged 1 commit into from
Jul 11, 2024
Merged

BUG: Call SetGlobalDefaultNumberOfThreads when processing "-threads" #1195

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions Core/Kernel/elxMainBase.cxx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -302,6 +302,11 @@ MainBase::SetMaximumNumberOfThreads() const
{
const int maximumNumberOfThreads = atoi(maximumNumberOfThreadsString.c_str());
itk::MultiThreaderBase::SetGlobalMaximumNumberOfThreads(maximumNumberOfThreads);

// The following statement (getting and setting GlobalDefaultNumberOfThreads) may look redundant, but it's not
// (using ITK 5.4.0)! The Set function ensures that GlobalDefaultNumberOfThreads <= GlobalMaximumNumberOfThreads.
// (GlobalDefaultNumberOfThreads is important, as ITK uses this number when constructing the ThreadPool.)
itk::MultiThreaderBase::SetGlobalDefaultNumberOfThreads(itk::MultiThreaderBase::GetGlobalDefaultNumberOfThreads());
}
} // end SetMaximumNumberOfThreads()

Expand Down
Loading