ruby.git/tool/ruby_vm/views/_leaf_helpers.erb, branch v4.0.3

Mark leaf defined instructions as leaf

2025-09-05T17:29:17+00:00

For example, `defined?(yield)` never calls a method, so it's leaf.

insns.def: Drop unused leafness_of_check_ints

2025-09-05T16:15:00+00:00

It was used to let MJIT override the leafness of the instruction when it
decides to remove check_ints for it. Now that MJIT is gone, nobody needs
to "override" the leafness using this.

[Feature #21116] Extract RJIT as a third-party gem

2025-02-13T09:01:03+00:00

Move the PC regardless of the leaf flag (#8232)

2023-08-17T03:28:33+00:00

Co-authored-by: Alan Wu

s/MJIT/RJIT/

2023-03-07T07:44:01+00:00

Fix incorrect line numbers in GC hook

2023-02-24T19:10:09+00:00

If the previous instruction is not a leaf instruction, then the PC was
incremented before the instruction was ran (meaning the currently
executing instruction is actually the previous instruction), so we
should not increment the PC otherwise we will calculate the source
line for the next instruction.

This bug can be reproduced in the following script:

```
require "objspace"

ObjectSpace.trace_object_allocations_start
a =

  1.0 / 0.0
p [ObjectSpace.allocation_sourceline(a), ObjectSpace.allocation_sourcefile(a)]
```

Which outputs: [4, "test.rb"]

This is incorrect because the object was allocated on line 10 and not
line 4. The behaviour is correct when we use a leaf instruction (e.g.
if we replaced `1.0 / 0.0` with `"hello"`), then the output is:
[10, "test.rb"].

[Bug #19456]

Remove DEFINED_IVAR2 from enum

2021-03-10T17:38:20+00:00

This version of defined? doesn't seem to be possible to emit anymore.

Lazily move PC with RUBY_VM_CHECK_INTS

2020-12-17T07:06:28+00:00

```
$ benchmark-driver -v --rbenv 'before --jit;after --jit' --repeat-count=12 --alternate --output=all benchmark.yml
before --jit: ruby 3.0.0dev (2020-12-17T06:17:46Z master 3b4d698e0b) +JIT [x86_64-linux]
after --jit: ruby 3.0.0dev (2020-12-17T07:01:48Z master 843abb96f0) +JIT [x86_64-linux]
last_commit=Lazily move PC with RUBY_VM_CHECK_INTS
Calculating -------------------------------------
                                 before --jit           after --jit
Optcarrot Lan_Master.nes    80.29343646660429     83.15779723251525 fps
                            82.26755637885149     85.50197941326810
                            83.50682959728820     88.14657804306270
                            85.01236533133049     88.78201988978667
                            87.81799334561326     88.94841008936447
                            87.88228562393064     89.37925215601926
                            88.06695585889995     89.86143277214475
                            88.84730834922165     90.00773346420887
                            90.46317871213088     90.82603371104014
                            90.96308347148916     91.29797694822179
                            90.97945938504556     91.31086331868738
                            91.57127890154500     91.49949184318844
```

Use ID instead of GENTRY for gvars. (#3278)

2020-07-03T07:56:44+00:00

Use ID instead of GENTRY for gvars.

Global variables are compiled into GENTRY (a pointer to struct
rb_global_entry). This patch replace this GENTRY to ID and
make the code simple.

We need to search GENTRY from ID every time (st_lookup), so
additional overhead will be introduced.
However, the performance of accessing global variables is not
important now a day and this simplicity helps Ractor development.

Avoid top-level search for nested constant reference from nil in defined?

2019-11-13T06:36:58+00:00

Fixes [Bug #16332]

Constant access was changed to no longer allow top-level constant access
through `nil`, but `defined?` wasn't changed at the same time to stay
consistent.

Use a separate defined type to distinguish between a constant
referenced from the current lexical scope and one referenced from
another namespace.