🐛 Fix Flags<N> data storage width #26995
Merged
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.
Description
Previously added unit tests identified that the storage for the Flags type was always 8 bits, even if many more flags than this were requested.
This was due to the incorrect use of
uvalue_t
instead ofbits_t
when definingflagbits_t
.This PR fixes the underlying root cause, and adjusts the unit tests to verify the intended edges cases for the class.
The actual impact of this bug was probably limited to uncommon machines with more than 8 axis. I believe that this could have caused some Axis to not move, when using every available axis in Marlin.