ChafaWorkCell: Linear scan for contrasting color pair#334
Merged
Conversation
hpjansson
requested changes
Jun 9, 2026
hpjansson
left a comment
Owner
There was a problem hiding this comment.
Looks good, but the commit message should read ChafaWorkCell: ... instead of chafa: .... By convention the latter refers to the CLI tool code.
abbb4dc to
bbed556
Compare
Owner
|
Thanks a lot for these PRs and the quick edit! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
chafa_work_cell_get_contrasting_color_pair previously relied on work_cell_get_dominant_channel, which performed a full counting sort over 4x64 RGBA values to determine the dominant channel and select the two extreme colors.
The result was used only for its min and max values. This change replaces the sort with a single linear scan that tracks min/max indices per channel directly.
The change is bit-identical on all test cases. It matches the old stable-sort tie-breaking behavior: the first occurrence wins for min, the last for max.
Performance
Linux x86_64, AMD Ryzen 9 7900X, GCC 15.2 -O2,
perf stat -r 3