Improve Jump Table Symbolization Algorithm #36
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.
I observed that RetroWrite missed some jump table entries when they refers to
the function boundary. The following assembly code that gcc-9 compiler emitted
represents the error case. Since the second jump table entry refers to label
.LBB38_624, which was defined at the function boundary, RetroWrite misses 6
jump table entries.
I added is_located_at_the_end_of_function() method to check function boundary
and define additional label to symbolize jump table entry. Also, I revised
symbolize_switch_tables() method to resolve the error.