diff options
author | Alan Wu <XrXr@users.noreply.github.com> | 2021-08-25 17:00:45 -0400 |
---|---|---|
committer | Alan Wu <XrXr@users.noreply.github.com> | 2021-10-20 18:19:39 -0400 |
commit | bd876c243aeace00ea312d0a5bbff091ccc84ba2 (patch) | |
tree | e30156ab87c3345a995dcd47c11dc9a535643694 /README.md | |
parent | 0562459473f44c270784074a09a33ea30d68e457 (diff) |
TracePoint support
This change fixes some cases where YJIT fails to fire tracing events.
Most of the situations YJIT did not handle correctly involves enabling
tracing while running inside generated code.
A new operation to invalidate all generated code is added, which uses
patching to make generated code exit at the next VM instruction
boundary. A new routine called `jit_prepare_routine_call()` is
introduced to facilitate this and should be used when generating code
that could allocate, or could otherwise use `RB_VM_LOCK_ENTER()`.
The `c_return` event is fired in the middle of an instruction as opposed
to at an instruction boundary, so it requires special handling. C method
call return points are patched to go to a fucntion which does everything
the interpreter does, including firing the `c_return` event. The
generated code for C method calls normally does not fire the event.
Invalided code should not change after patching so the exits are not
clobbered. A new variable is introduced to track the region of code that
should not change.
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 1 |
1 files changed, 0 insertions, 1 deletions
@@ -32,7 +32,6 @@ To cite this repository in your publications, please use this bibtex snippet: YJIT is a work in progress and as such may not yet be mature enough for mission-critical software. Below is a list of known limitations, all of which we plan to eventually address: -- No support for the `TracePoint` API (see [#54](https://github.com/Shopify/yjit/issues/54)). - No garbage collection for generated code. Because there is no GC for generated code yet, your software could run out of executable memory if it is large enough. You can change how much executable memory is allocated using [YJIT's command-line options](https://github.com/Shopify/yjit#command-line-options). |