[build] make generated .class files deterministic#7784
Merged
kares merged 2 commits intojruby:jruby-9.3from May 25, 2023
Merged
[build] make generated .class files deterministic#7784kares merged 2 commits intojruby:jruby-9.3from
kares merged 2 commits intojruby:jruby-9.3from
Conversation
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 PR contains 2 commits which should make the generated .class files more deterministic.
Essentially the problem is
Class#getDeclaredMethodsreturns an undefined order, so even when a simple patch is applied to a stable version one ends up with a ton of .class files (mostly the "INVOKER" ones) modified in the resulting artifact (jruby-base.jar).sample diff after re-compiling and decompiling
org/jruby/RubyArray\$INVOKER\$i\$all_p.classusingjavap(nothing was changed against stable 9.3.10.0 the difference is likely just a different Java or OS version):NOTE: all of the code touched here should only be used during compilation - thus "if compiles" should be fairly low risk.