-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade zlib to 1.3.1 #99472
Upgrade zlib to 1.3.1 #99472
Conversation
"implicit-int-conversion" warning The change to deflate.c is legal because 'len' has an upper bound of MAX_STORED, which means it fits cleanly into a 16-bit integer. So writing out 2x 8-bit values will not result in data loss. The change to trees.c is legal because within this loop, 'count' is intended to have an upper bound of 138, with the target assignment only executing if 'count' is bounded by 4. Neither the 'count' local in isolation nor the addition that's part of the target line is expected to result in integer overflow. But even if it did, that's a matter for a different warning code and doesn't impact the correctness of the narrowing cast being considered here. Author: Levi Broderick <[email protected]>
Tagging subscribers to this area: @dotnet/area-system-io-compression |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, modulo what appears to be a stray readme deletion. I diffed the files against the zlib repo and the only changes are what are documented in our readme file.
@ericstj @GrabYourPitchforks @artl93 Edit: Rerunning perf in a Windows arm64 machine, I ran it in x64 and that uses zlib-intel... |
@ericstj @GrabYourPitchforks @artl93 here are the results in Windows arm64, which actually consumes zlib (not zlib-intel). There wasn't any significant perf difference. Note that new is top, base is bottom:
|
Looks good. We can also double-check the results from the perf-lab since this is merged now. Looks like we have some ZLIB benchmarks that will run on more platforms. I think that's https://pvscmdupload.blob.core.windows.net/reports/allTestHistory/TestHistoryIndexIndex.html |
Sure, I can also check those results. First I need to understand if they get executed periodically in an automated way or if I need to execute them myself manually. Since the servicing branches are currently closed, would anyone object to merging the servicing PRs so they bake in staging until the branches open again? |
No description provided.