| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Co-authored-by: Irit Katriel <1055913+iritkatriel@users.noreply.github.com>
|
So, on the JIT branch, we don't actually keep the executor handy when executing instructions (only when entering/exiting traces). I'm guessing we'll need it a lot more in the future once we start doing stitching and such, but I wonder: can we just stick it on the tstate or the frame? It feels a bit painful to dedicate a register to this thing, especially since it'll be hardly used in optimized traces (I think). Not a big deal though, and can be deferred to a later date. Just something to ponder, or to do if it's easy now. |
Sorry, something went wrong.
|
Idea: put the executor's address in _CHECK_VALIDITY's operand? Then the JIT would require no modifications to support this change. |
Sorry, something went wrong.
|
Ah, never mind, the JIT can burn in the executor. I withdraw my comments. :) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes GH-109369.
Adds a _CHECK_VALIDITY uop which is inserted after any escaping operations.
Ensures that uop traces will be exited promptly if the code is instrumented.