ruby.git/test/ruby/test_optimization.rb, branch v3_2_11 The Ruby Programming Language merge revision(s) e1104017e3080fd432c0b5fdc3ae6e004ffd0834: [Backport #19781] 2024-07-20T06:12:36+00:00 nagachika nagachika@ruby-lang.org 2024-07-20T06:12:36+00:00 2ac8e2049bad37da38576b1ed263713c66eba2c9 YJIT: Fix cfp inconsistency on tailcall (#8107) [Bug #19781] 
	YJIT: Fix cfp inconsistency on tailcall (#8107)

	[Bug #19781]
Use omit instead of skip: test/ruby/**/*.rb 2022-01-04T08:25:30+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2022-01-04T08:25:30+00:00 47bf64a26d3d95a312ea5cf5d94ee1d2104f5e26 






Prepare for removing RubyVM::JIT (#5262)
2021-12-14T07:07:46+00:00

Takashi Kokubun
takashikkbn@gmail.com

2021-12-14T07:07:46+00:00

1a63468831524f68e73cbb068071652c6486cfc6












Optimize dynamic string interpolation for symbol/true/false/nil/0-9
2021-11-18T23:10:20+00:00

Jeremy Evans
code@jeremyevans.net

2021-11-18T23:10:20+00:00

b08dacfea39ad8da3f1fd7fdd0e4538cc892ec44

This provides a significant speedup for symbol, true, false,
nil, and 0-9, class/module, and a small speedup in most other cases.

Speedups (using included benchmarks):
:symbol        :: 60%
0-9            :: 50%
Class/Module   :: 50%
nil/true/false :: 20%
integer        :: 10%
[]             :: 10%
""             :: 3%

One reason this approach is faster is it reduces the number of
VM instructions for each interpolated value.

Initial idea, approach, and benchmarks from Eric Wong. I applied
the same approach against the master branch, updating it to handle
the significant internal changes since this was first proposed 4
years ago (such as CALL_INFO/CALL_CACHE -> CALL_DATA). I also
expanded it to optimize true/false/nil/0-9/class/module, and added
handling of missing methods, refined methods, and RUBY_DEBUG.

This renames the tostring insn to anytostring, and adds an
objtostring insn that implements the optimization. This requires
making a few functions non-static, and adding some non-static
functions.

This disables 4 YJIT tests.  Those tests should be reenabled after
YJIT optimizes the new objtostring insn.

Implements [Feature #13715]

Co-authored-by: Eric Wong <e@80x24.org>
Co-authored-by: Alan Wu <XrXr@users.noreply.github.com>
Co-authored-by: Yusuke Endoh <mame@ruby-lang.org>
Co-authored-by: Koichi Sasada <ko1@atdot.net>




This provides a significant speedup for symbol, true, false,
nil, and 0-9, class/module, and a small speedup in most other cases.

Speedups (using included benchmarks):
:symbol        :: 60%
0-9            :: 50%
Class/Module   :: 50%
nil/true/false :: 20%
integer        :: 10%
[]             :: 10%
""             :: 3%

One reason this approach is faster is it reduces the number of
VM instructions for each interpolated value.

Initial idea, approach, and benchmarks from Eric Wong. I applied
the same approach against the master branch, updating it to handle
the significant internal changes since this was first proposed 4
years ago (such as CALL_INFO/CALL_CACHE -> CALL_DATA). I also
expanded it to optimize true/false/nil/0-9/class/module, and added
handling of missing methods, refined methods, and RUBY_DEBUG.

This renames the tostring insn to anytostring, and adds an
objtostring insn that implements the optimization. This requires
making a few functions non-static, and adding some non-static
functions.

This disables 4 YJIT tests.  Those tests should be reenabled after
YJIT optimizes the new objtostring insn.

Implements [Feature #13715]

Co-authored-by: Eric Wong <e@80x24.org>
Co-authored-by: Alan Wu <XrXr@users.noreply.github.com>
Co-authored-by: Yusuke Endoh <mame@ruby-lang.org>
Co-authored-by: Koichi Sasada <ko1@atdot.net>






Make Array#min/max optimization respect refined methods
2021-09-30T22:18:14+00:00

Jeremy Evans
code@jeremyevans.net

2021-09-30T22:18:14+00:00

1f5f8a187adb746b01cc95c3f29a0a355f513374

Pass in ec to vm_opt_newarray_{max,min}. Avoids having to
call GET_EC inside the functions, for better performance.

While here, add a test for Array#min/max being redefined to
test_optimization.rb.

Fixes [Bug #18180]




Pass in ec to vm_opt_newarray_{max,min}. Avoids having to
call GET_EC inside the functions, for better performance.

While here, add a test for Array#min/max being redefined to
test_optimization.rb.

Fixes [Bug #18180]






Fix warnings in test_optimization.rb
2021-08-24T15:34:48+00:00

Jeremy Evans
code@jeremyevans.net

2021-08-24T15:34:48+00:00

14a9c364f75a9729d5a49e1fbea08fec2f813bdd

These were introduced in the test for tracing optimized methods
added in 48c8df9e0eb295af06d593ce37ce1933c0ee1d90.





These were introduced in the test for tracing optimized methods
added in 48c8df9e0eb295af06d593ce37ce1933c0ee1d90.







Allow tracing of optimized methods
2021-08-21T17:15:01+00:00

Jeremy Evans
code@jeremyevans.net

2021-08-21T17:15:01+00:00

48c8df9e0eb295af06d593ce37ce1933c0ee1d90

This updates the trace instructions to directly dispatch to
opt_send_without_block.  So this should cause no slowdown in
non-trace mode.

To enable the tracing of the optimized methods, RUBY_EVENT_C_CALL
and RUBY_EVENT_C_RETURN are added as events to the specialized
instructions.

Fixes [Bug #14870]

Co-authored-by: Takashi Kokubun <takashikkbn@gmail.com>




This updates the trace instructions to directly dispatch to
opt_send_without_block.  So this should cause no slowdown in
non-trace mode.

To enable the tracing of the optimized methods, RUBY_EVENT_C_CALL
and RUBY_EVENT_C_RETURN are added as events to the specialized
instructions.

Fixes [Bug #14870]

Co-authored-by: Takashi Kokubun <takashikkbn@gmail.com>






Rename RubyVM::MJIT to RubyVM::JIT
2021-01-14T06:46:51+00:00

Takashi Kokubun
takashikkbn@gmail.com

2021-01-14T06:36:45+00:00

e1fee7f949cb6719122672fa1081c60984a5339f

because the name "MJIT" is an internal code name, it's inconsistent with
--jit while they are related to each other, and I want to discourage future
JIT implementation-specific (e.g. MJIT-specific) APIs by this rename.

[Feature #17490]





because the name "MJIT" is an internal code name, it's inconsistent with
--jit while they are related to each other, and I want to discourage future
JIT implementation-specific (e.g. MJIT-specific) APIs by this rename.

[Feature #17490]







Guard all accesses to RubyVM::MJIT with defined?(RubyVM::MJIT) &&
2020-12-04T15:45:54+00:00

Benoit Daloze
eregontp@gmail.com

2020-12-04T15:40:02+00:00

b4ec4a41c24105efbb43f9b70ca7f36d22f98294

* Otherwise those tests, etc cannot run on alternative Ruby implementations.





* Otherwise those tests, etc cannot run on alternative Ruby implementations.







disable GC on a test
2020-06-09T06:52:25+00:00

Koichi Sasada
ko1@atdot.net

2020-06-09T06:52:25+00:00

195075e8f5f2220a0a1f00f5cfd2ad98681e71d5

CI fails with GC while `foo{}`, so that disable GC for this script.





CI fails with GC while `foo{}`, so that disable GC for this script.