diff options
| author | Takashi Kokubun <takashikkbn@gmail.com> | 2022-12-24 01:13:40 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-12-24 01:13:40 -0800 |
| commit | b9332ac8e7126066ac4238443d63eaa4c06789f9 (patch) | |
| tree | 1d3d45ec28ddbcc7e124d026540be61cf4ef3840 /tool | |
| parent | d521c9e5a7ed603f8f1aaa9a9a66c3cc80599b0c (diff) | |
MJIT: Cancel all on disastrous situations (#7019)
I noticed this while running test_yjit with --mjit-call-threshold=1,
which redefines `Integer#<`. When Ruby is monkey-patched,
MJIT itself could be broken.
Similarly, Ruby scripts could break MJIT in many different ways. I
prepared the same set of hooks as YJIT so that we could possibly
override it and disable it on those moments. Every constant under
RubyVM::MJIT is private and thus it's an unsupported behavior though.
Notes
Notes:
Merged-By: k0kubun <takashikkbn@gmail.com>
Diffstat (limited to 'tool')
| -rwxr-xr-x | tool/mjit/bindgen.rb | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/tool/mjit/bindgen.rb b/tool/mjit/bindgen.rb index c093cd423c..a966a46944 100755 --- a/tool/mjit/bindgen.rb +++ b/tool/mjit/bindgen.rb @@ -353,10 +353,11 @@ generator = BindingGenerator.new( VM_METHOD_TYPE_ISEQ ], UINT: %w[ - SHAPE_ID_NUM_BITS + RUBY_EVENT_CLASS SHAPE_CAPACITY_CHANGE SHAPE_FLAG_SHIFT SHAPE_FROZEN + SHAPE_ID_NUM_BITS SHAPE_INITIAL_CAPACITY SHAPE_IVAR SHAPE_ROOT |