diff options
| author | nagachika <nagachika@ruby-lang.org> | 2023-07-16 11:22:31 +0900 |
|---|---|---|
| committer | nagachika <nagachika@ruby-lang.org> | 2023-07-16 11:25:45 +0900 |
| commit | 0ba10fd8508b1a2bf7488649ee90622de9bef04a (patch) | |
| tree | db2df5b1004882374f4dcad19e5372f7e43dce5c /test/ruby/test_stack.rb | |
| parent | 2f603bc4d750384d57513679ca9db2b4e2e3ec34 (diff) | |
merge revision(s) 132934b82baad97107fe754d60f9a68a1db7ecda: [Backport #19463]
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][1] while we were
refactoring to use the current backend. Later, we had a chance to spot
this issue while [preparing][2] to enable unused variable warnings, but
didn't spot the issue.
Fixes [Bug #19463]
[1]: 27fcab995e6dde19deb91dc6e291bdb72100af68
[2]: 31461c7e0eab4963ccc8649ea8ebf27979132c0c
---
test/ruby/test_yjit.rb | 41 +++++++++++++++++++++++++++++++++++++++++
yjit/src/codegen.rs | 4 ++--
2 files changed, 43 insertions(+), 2 deletions(-)
Diffstat (limited to 'test/ruby/test_stack.rb')
0 files changed, 0 insertions, 0 deletions