[objects] Take into account the LSB bit in purecap ABI in Code::GetOffsetFromInstructionStart #5
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.
When the PCC is sealed in purecap ABI, the LSB bit is set, leading to an off-by-one error in the computation of the offset from the instruction start to the current PCC address. This can cause errors such as in
OptimizedFrame::LookupExceptionHandlerInTable, where the computed offset is used to look up an exception handler table.Without this patch, executing the following JS code using
./d8 --allow-natives-syntax ~/v8-work/turbofan-exception-missing-code.js:leads to an exception after the function
a()is optimised by Turbofan becauseOptimizedFrame::LookupExceptionHandlerInTablecould not find the exception handler:With the patch, the script doesn't raise an exception as the ReferenceError is caught.