Structure peer-site selector trace candidates
This commit is contained in:
parent
0242fb85f8
commit
3d78123e28
2 changed files with 35 additions and 0 deletions
|
|
@ -106,6 +106,11 @@ Working rule:
|
|||
`0x00420030 / 0x00420280 / 0x0047efe0 / 0x0047fd50` consume the resulting selector, with the
|
||||
current first target being the save-backed
|
||||
`0x0045c150 -> 0x0045c310 -> 0x0045c36e -> 0x00456100` family
|
||||
- use the structured periodic-company trace candidate fields now checked into
|
||||
`inspect-periodic-company-service-trace`: owner strip
|
||||
`0x0045c150 -> 0x0045c310 -> 0x0045c36e -> 0x00456100 -> 0x00455b70`, persisted tag
|
||||
`0x5dc1`, selector lane `[owner+0x23e]`, and helper linkage
|
||||
`0x0040ceab -> 0x0045c150` / `0x0040d1a1 -> 0x0045c310`
|
||||
- decide whether the direct `0x0040ceab / 0x0040d1a1` linkage is enough to treat that
|
||||
save-backed owner family as the same class-0 site family consumed by
|
||||
`0x00420030 / 0x00420280 / 0x0047efe0 / 0x0047fd50`, or whether one more helper-field bridge
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue