todo: correct self-modifying region caveat

1 files changed, 1 insertions, 1 deletions

diff --git a/TODO.md b/TODO.md
index 711340a..37d17ef 100644
--- a/TODO.md
+++ b/TODO.md
@@ -532,7 +532,7 @@ brief someone without re-reading the code.
 - [ ] x86-64 jit, phase 2 follow-ups (phase 2 is in the done list). we are not chasing llvm parity on the jit (owner's decision).
   - region 474..692 in `tests/programs/o3.zc` falls back to the region interpreter; find out why and compile it.
   - fib is slightly slower under o3 than plain (0.86 against 0.78 ms), likely region entry and exit on every recursive call; related to direct o3-to-o3 calls.
-  - the self-modifying-region caveat: compiled regions don't see code that rewrites itself inside a region; document it or invalidate the compiled region.
+  - a compiled o3 region that stores into its own code finishes the current activation on the old code; the change takes effect on the next entry. either document it or bail to the region interpreter when the hook drops the running region.
 - [ ] (in progress on work/exactsize) exact-size bounds checks: n is stored in p[-4] bits 32..62 and the check is 2 loads.
 - [ ] (in progress on work/checks) loop-entry check hoisting, dropping checks proven safe by `len()` or a known size, and `--explain-checks` v1 json: header `{"version":1}`, then one line per kept check with file, line, col, end_line, end_col, fn, kind, loop_depth, reason, fix and an optional edit.
 - [ ] (in progress on work/bench) `make bench`, `bench-check` and `bench-selftest`: baseline from ec49c6d, jit and llvm rows, interp rows only with `INTERP=1`. follow-up: fill the checks column from `--explain-checks` and re-save the baseline; the rule that fails when the check count rises is already in bench-check.