From: shevegen@... Date: 2018-02-19T07:50:47+00:00 Subject: [ruby-core:85637] [Ruby trunk Feature#14491] MJIT needs internal debugging methods Issue #14491 has been updated by shevegen (Robert A. Heiler). Not sure about the method-names above, but I agree with the reasoning; we have methods on "GC." too so I think it would be nice to be able to have some finer control over mjit as well. ---------------------------------------- Feature #14491: MJIT needs internal debugging methods https://bugs.ruby-lang.org/issues/14491#change-70428 * Author: sam.saffron (Sam Saffron) * Status: Open * Priority: Normal * Assignee: * Target version: ---------------------------------------- ### Issue Doing careful analysis of MJIT performance is very hard cause there is no way of instrumenting this in runtime ### Proposal 1. Add `MJIT.enable`, `MJIT.disable`, `MJIT.pause` methods. - `MJIT.pause` will continue using MJIT for execution but will no longer compile new fragments 2. Add `MJIT.trace` or similar that returns a block for key compile start / compile end operations. ``` MJIT.trace do |klass, method, line, operation, duration| end ``` This will allow simpler analysis of MJITs performance. -- https://bugs.ruby-lang.org/ Unsubscribe: