Feature #21116: Extract RJIT as a third-party gem

• Status: Closed
• Assignee: -
• Target version: -

[k0kubun (Takashi Kokubun)]

Proposal

• Extract the implementation of RJIT::C to ruby/rjit and publish it as a thirt-party gem rjit
• Allow jit_exec() to call body->jit_entry even when --yjit is not given
• Remove RJIT from the Ruby core
  • Remove --rjit flags and RubyVM::RJIT

Background

• RJIT depends on fiddle, and fiddle has been extracted as a bundled gem. @hsbt (Hiroshi SHIBATA) and @nobu (Nobuyoshi Nakada) are struggling to maintain the dependency from the Ruby core to a bundled gem.
• Integrating RJIT into the Ruby core has forced VM maintainers to update RJIT with every VM change, significantly increasing the maintenance burden.
• I thought you couldn't implement the core of RJIT as a third-party gem when I introduced RJIT [Feature #19420]. However, now @tenderlovemaking (Aaron Patterson) and I think it's possible if we modify jit_exec() as explained in the proposal.

[k0kubun (Takashi Kokubun)]

• Related to Feature #19420: Simplify MJIT implementation added

[k0kubun (Takashi Kokubun)]

• Description updated (diff)

[k0kubun (Takashi Kokubun)]

• Description updated (diff)

[k0kubun (Takashi Kokubun)]

• Description updated (diff)

[k0kubun (Takashi Kokubun)]

• Description updated (diff)

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed

Applied in changeset git|4a67ef09ccd703047552b740431cfe15e32451f4.

---

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

[tenderlovemaking (Aaron Patterson)]

• Related to Feature #21140: Add a method to get the address of certain JIT related functions added