ruby.git/mjit.h, branch v3_2_11

MJIT: Cancel all on disastrous situations (#7019)

2022-12-24T09:13:40+00:00

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.

MJIT: Give a more appropriate name to the initial state

2022-12-09T06:58:40+00:00

MJIT: Drop an obsoleted explanation [ci skip]

2022-12-09T06:40:56+00:00

There's no MJIT worker thread anymore

Use a ruby-lang alias [ci skip]

2022-12-09T06:40:56+00:00

MJIT: Refactor mjit_wait

2022-12-07T07:21:19+00:00

MJIT: Remove obsoleted MJIT counters

2022-12-07T07:05:00+00:00

MJIT: Refactor the jit_func enum for MJIT

2022-12-07T05:36:58+00:00

All values should have a MJIT_ prefix. We could address the warning for
the end mark if we just define the macro for the check next to the enum.
It even simplifies some code for checking the enum.

Rename --mjit-min-calls to --mjit-call-threshold (#6731)

2022-11-15T07:38:52+00:00

for consistency with YJIT

s/mjit_func_t/jit_func_t/

2022-11-13T22:41:08+00:00

Make mjit_cont sharable with YJIT (#6556)

2022-10-17T16:27:59+00:00

* Make mjit_cont sharable with YJIT

* Update dependencies

* Update YJIT binding