ruby.git/lib/ruby_vm/mjit/hooks.rb, branch v3_2_11 The Ruby Programming Language MJIT: Cancel all on disastrous situations (#7019) 2022-12-24T09:13:40+00:00 Takashi Kokubun takashikkbn@gmail.com 2022-12-24T09:13:40+00:00 b9332ac8e7126066ac4238443d63eaa4c06789f9 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. 
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.