remove unnecessary allocations in HistogramSumReducer #6132
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contributes to #4705.
Int32HistogramSumReducer
andInt16HistogramSumReducer
allocate anint
and assign to it the value ofOMP_NUM_THREADS()
, then only use that value immediately after, for one OpenMP for loop.This PR proposes just directly passing
OMP_NUM_THREADS()
to the configuration for those OpenMPfor
loop pragmas, to avoid the unnecessary allocation.This also resolves the following compiler warnings that show up on
clang
when OpenMP support is disabled:How I tested this
LightGBM's CI covers the cases where OpenMP is available. I ran the following locally to confirm that this suppresses the compiler warnings when building without OpenMP support.
rm -rf ./build mkdir ./build cd ./build cmake -DUSE_OPENMP=off .. make -j3 _lightgbm