Fix undefined behavior in pixel get/set routines #4141
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.
The unit tests only seem to exercise the UB in set_pixel_color, but I believe the same issue is present in get_pixel_color. There is no guarantee that the incoming pixel buffer is aligned, so casting it to a larger integer with alignment requirements can issue an unaligned load.
I've unified and simplified the LE/BE implementation divergence as much as possible. memcpy() should compile to roughly the same asm as a direct assignment. Tested on LE and BE.
Should fix #1313