From: sam.saffron@... Date: 2018-02-19T01:40:57+00:00 Subject: [ruby-core:85626] [Ruby trunk Bug#14491] MJIT needs internal debugging methods Issue #14491 has been reported by sam.saffron (Sam Saffron). ---------------------------------------- Bug #14491: MJIT needs internal debugging methods https://bugs.ruby-lang.org/issues/14491 * Author: sam.saffron (Sam Saffron) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- ### 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: