Issue #14491 has been updated by k0kubun (Takashi Kokubun).
> MJIT.enable, MJIT.disable, MJIT.pause, MJIT.trace
Could you describe some detailed use cases (some possible problem which can be effectively investigated by them, and what code would be written for the investigation) for each method? Any feature request requires it and I think it's not detailed enough for now.
----------------------------------------
Feature #14491: MJIT needs internal debugging methods
https://bugs.ruby-lang.org/issues/14491#change-70442
* 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: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>