Fixed indexOutOfBounds bug when the last bytecode of a function has 0 size #9
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.
If a label or any bytecode with size 0 is the last bytecode of a function. There will be an index out of bounds exception at at cafebabe.CodeHandler$$anonfun$computeMaxStack$1.apply(CodeHandler.scala:156)
This is caused by the following code in CodeHandler.scala
actualSize is calculated as the sum of size of all instructions where the size of a label instruction is 0. But if a label is at the end of the bytecode list, and the value of pc will equal to the the calculated actualSize therefore caused the index out of bounds exception on the codeArray.