From: "Eregon (Benoit Daloze)" Date: 2021-12-30T20:17:30+00:00 Subject: [ruby-core:106927] [Ruby master Feature#18440] YJIT is enabled if any YJIT tuning options are set Issue #18440 has been updated by Eregon (Benoit Daloze). I think only enabling on explicit --jit/--yjit/--mjit is better because it's more intuitive. If e.g. ` --yjit-exec-mem-size=32` is in RUBYOPT it seems unexpected that it would enable YJIT without any `--yjit` anywhere. ---------------------------------------- Feature #18440: YJIT is enabled if any YJIT tuning options are set https://bugs.ruby-lang.org/issues/18440#change-95748 * Author: georgeclaghorn (George Claghorn) * Status: Open * Priority: Normal ---------------------------------------- I was testing YJIT in a Rails app with `RUBYOPT="--yjit --yjit-exec-mem-size=32"`. I saw some weird issues around Rails view caching, so I attempted to temporarily disable YJIT by removing `--yjit` and leaving the tuning options in place (`RUBYOPT="--yjit-exec-mem-size=32"`). However, YJIT remained enabled until I also removed `--yjit-exec-mem-size=32`. ``` $ ruby -e 'puts RubyVM::YJIT.runtime_stats.inspect' nil $ ruby --yjit-exec-mem-size -e 'puts RubyVM::YJIT.runtime_stats.inspect' {:inline_code_size=>378495, :outlined_code_size=>311079} ``` I expected removing `--yjit` to disable YJIT and was surprised by this. -- https://bugs.ruby-lang.org/ Unsubscribe: