ruby.git/lib/ruby_vm/mjit, branch v3_2_11

MJIT: Check if self is T_OBJECT before opt_pc jump

2023-06-02T09:55:53+00:00

merge revision(s) fc03ba50f1ff6c30f7c654f564b4dffbed0844ef: [Backport #19263]

2022-12-27T05:56:51+00:00

	MJIT: Fix JIT code for multiple values in a single case

	[Bug #19263]
	---
	 lib/ruby_vm/mjit/compiler.rb |  2 +-
	 test/ruby/test_mjit.rb       | 10 ++++++++++
	 2 files changed, 11 insertions(+), 1 deletion(-)

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.

Remove MJIT's private constants from docs [ci skip]

2022-12-22T19:35:46+00:00

Put RubyVM::MJIT::Compiler under ruby_vm directory (#6989)

2022-12-22T06:46:15+00:00

[Misc #19250]