-
Notifications
You must be signed in to change notification settings - Fork 627
Closed handle long constant values in the OpcodeStack #688
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
Conversation
Currently we have test failures like below:
|
How is that possible when we've checked that Edit: Hang on, where are we even getting |
It happens in MethodHandle class updated by Java9. I guess that Java9 javac changed some behavior, but cannot find related document. →Update: it is not related with javac behavior, it it caused just by new implementation in MethodHandles.loop() method. i could reproduce it with Java8, see unit test in this PR. |
@ThrawnCA please have a review again, I've added test case to reproduce problem with |
SonarQube analysis reported 4 issues Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:
|
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.
Really? We need to handle booleans and arrays as if they were numbers?
Eww. I'll approve, but eww.
Not array, just a boxed types. I'll merge this PR. |
Wait, I remember this. @mebigfatguy Didn't you discover that the compiler saves array length as a Edit: Found it: mebigfatguy/fb-contrib#40 (comment) |
@mebigfatguy Bump. I know this is merged, but do you have more insight on what the compiler is doing here? |
Same with #514 but rebased on the top of
release-3.1
branch.