Update pylauncher.exe#27225
Open
sbc100 wants to merge 1 commit into
Open
Conversation
This executable was pulled from the latest win32 build on the emscripten-releases waterfall: https://storage.googleapis.com/webassembly/emscripten-releases-builds/win/2650e4f60d08b155fbe8b01140ea1e8527cb55ac/wasm-binaries.zip This includes emscripten-core#27169, which I confirmed by running `strings -l` on the binary before and after.
Collaborator
Author
|
I can't really explain how the binary size is identical both before and after? Maybe there some kind of padding which hides the extra |
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 executable was pulled from the latest win32 build on the emscripten-releases waterfall:
https://storage.googleapis.com/webassembly/emscripten-releases-builds/win/2650e4f60d08b155fbe8b01140ea1e8527cb55ac/wasm-binaries.zip
This includes #27169, which I confirmed by running
strings -lon the binary before and after.