perf: avoid zero-initializing modular channel payloads#712
Open
hjanuschka wants to merge 1 commit intolibjxl:mainfrom
Open
perf: avoid zero-initializing modular channel payloads#712hjanuschka wants to merge 1 commit intolibjxl:mainfrom
hjanuschka wants to merge 1 commit intolibjxl:mainfrom
Conversation
Benchmark @ 2c27f27Comparing: e883140e (Base) vs 5b261fb2 (PR)
|
17 tasks
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.
This adds an uninitialized image constructor that zeros only offset/padding regions, then uses it for modular channel allocation. It removes large buffer zeroing work in hot decode paths while preserving prediction boundary behavior. Unsafe is confined to allocation/row access internals and is safe because modular decode fully writes the data region before any read, and padding is explicitly zeroed.