Optimize Linux GTK dirty pixel conversion - #434
Merged
Merged
Conversation
Linux GTK now uses retained damage metadata to limit RGBA8-to-premultiplied-ARGB32 conversion to affected device pixels. First presentations, resized or reallocated buffers, and invalid damage inputs retain the full-conversion fallback, while valid rectangles are normalized, scaled, rounded outward, and clipped safely. A GTK-independent pixel helper and focused C regression suite cover conversion correctness, stride padding, buffer reuse, edge cases, and preservation of untouched pixels; the focused step is also wired into `zig build test`. Factory-Run: 43e0b2dd7071a93d10b5410937a13e50 Co-authored-by: Sepehr Safari <25853688+sepehr-safari@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Linux GTK now uses retained damage metadata to limit RGBA8-to-premultiplied-ARGB32 conversion to affected device pixels. First presentations, resized or reallocated buffers, and invalid damage inputs retain the full-conversion fallback, while valid rectangles are normalized, scaled, rounded outward, and clipped safely.
A GTK-independent pixel helper and focused C regression suite cover conversion correctness, stride padding, buffer reuse, edge cases, and preservation of untouched pixels; the focused step is also wired into
zig build test.