Optimize #57
Merged
Optimize #57
Conversation
This file contains 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
|
Yay! |
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.
stb_image: PNG/zlib decoder optimizations.
The goal was to focus on low-complexity, high-yield changes: improve
decoding speed significantly while staying with the original spirit of
the library.
This is more than 2x faster on my machine when decoding my 1680x1050
24-bit test PNG (screenshot of a website) - very scientific, I know.
Nevertheless, there's nothing particularly data-sensitive in here. The
one thing that is specific to that particular file is that I added a
fast path for the "none" filter when img_n == out_n (i.e. just do a
memcpy). But that's such a trivial change (and likely to benefit other
files, since "none" is common) that I don't feel guilty about it.