YJIT: Generate Block::entry_exit with block entry PC
Previously, when Block::entry_exit is requested from any instruction
that is not the first one in the block, we generated the exit with an
incorrect PC. We should always be using the PC for the entry of the
block for Block::entry_exit.
It was a simple typo. The bug was introduced while we were
refactoring to use the current backend. Later, we had a chance to spot
this issue while preparing to enable unused variable warnings, but
didn't spot the issue.
Added by alanwu (Alan Wu) over 2 years ago
YJIT: Generate Block::entry_exit with block entry PC
Previously, when Block::entry_exit is requested from any instruction
that is not the first one in the block, we generated the exit with an
incorrect PC. We should always be using the PC for the entry of the
block for Block::entry_exit.
It was a simple typo. The bug was introduced while we were
refactoring to use the current backend. Later, we had a chance to spot
this issue while preparing to enable unused variable warnings, but
didn't spot the issue.
Fixes [Bug #19463]