Narrow peer-site selector source lanes

This commit is contained in:
Jan Petykiewicz 2026-04-18 18:49:16 -07:00
commit 359350f6c5
2 changed files with 13 additions and 5 deletions

View file

@ -75,6 +75,9 @@ Working rule:
- `0x0045c36e / 0x0045da65 / 0x0045e0fc` are concrete callers of `0x00456100`, repeatedly
allocating `0x23a` rows, forwarding stack-backed buffers, and using the same default scalar
lanes
- the `0x00456100 -> 0x00455b70` wrapper mapping is now grounded far enough to say the sampled
selector-source lanes are `[owner+0x23e]` at `0x0045c36e`, literal zero at `0x0045da65`, and
`[ebp+0x08]` at `0x0045e0fc`
- `0x00485819` is one typed placed-structure caller of `0x0052edf0` through the generic
three-arg wrapper `0x00530640`
- `0x00490a79` is one chooser-side caller of `0x00455b70`, feeding literal selector
@ -97,7 +100,8 @@ Working rule:
`0x00420030 / 0x00420280 / 0x0047efe0 / 0x0047fd50` consume the resulting selector, with the
current first target being the dense `0x0045c36e / 0x0045da65 / 0x0045e0fc -> 0x00456100`
family
- name the persisted lane that reaches selector arg `3` inside that wrapper bundle
- name which of the currently sampled selector-source lanes (`[owner+0x23e]`, literal zero, or
`[ebp+0x08]`) reaches selector arg `3` for the live site rows
- Use the higher-layer probes as the standard entry point for the current blocked frontier instead
of generic save scans:
`runtime inspect-periodic-company-service-trace <save.gms>`,