v5.0.x: opal_bitmap.c: fix logic error in length of array #13606
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.
This is a v5.0.x PR corresponding to main PR #13597.
Only one of the three commits on the main PR was relevant to the v5.0.x branch, so this PR only has a cherry pick of that one commit (7bbdb0a):
Inspired by some fixes in PMIx:
Fix some logic errors in opal_bitmap.c:opal_num_set_bits(): the parameter is supposed to be the number of bits, not number of elements. The fixes here are essentially the same as Matthew's, but with some stylistic changes.
It doesn't look like this function is invoked anywhere in the code base, which is why we hadn't previously noticed these issues.
That being said, if we have the code, it should be correct. This commit therefore also adds some tests for the
opal_bitmap_num_set_bits() function to "make check" to make sure that it's actually working properly.
(cherry picked from commit 7bbdb0a)