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.

1 files changed, 12 insertions, 0 deletions

diff --git a/test/ruby/test_mjit.rb b/test/ruby/test_mjit.rb
index c616ac2313..399bf20071 100644
--- a/test/ruby/test_mjit.rb
+++ b/test/ruby/test_mjit.rb
@@ -1177,6 +1177,18 @@ class TestMJIT < Test::Unit::TestCase
     end;
   end
 
+  def test_cancel_by_bop_redefinition
+    assert_eval_with_jit("#{<<~"begin;"}\n#{<<~"end;"}", success_count: 0, call_threshold: 2)
+    begin;
+      class Integer
+        def <(x)
+          true
+        end
+      end
+      2.times {}
+    end;
+  end
+
   def test_caller_locations_without_catch_table
     out, _ = eval_with_jit("#{<<~"begin;"}\n#{<<~"end;"}", call_threshold: 2)
     begin;