diff options
| author | Aaron Patterson <tenderlove@ruby-lang.org> | 2019-08-05 11:32:42 -0700 |
|---|---|---|
| committer | Aaron Patterson <tenderlove@ruby-lang.org> | 2019-08-05 13:31:58 -0700 |
| commit | 81252c5ccd15295155a8fe30b0b56117ba7c79e7 (patch) | |
| tree | 05cb7e325bbd51591a0f943c6778c118e84a1be5 /COPYING | |
| parent | c9192ef2e8793fd870a4af40f422bc939a135ef9 (diff) | |
| download | ruby-81252c5ccd15295155a8fe30b0b56117ba7c79e7.tar.gz | |
Let prev EP move again
The last time we committed this, we were asking the VM to write to the
ep. But VM assertions check if the ENV data is the correct type, which
if it's a T_MOVED pointer it's not the correct type. So the vm
assertions would fail. This time we just directly write to it from the
GC and that bypasses the vm assertion checks.
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions