Ground add-building compact span semantics
This commit is contained in:
parent
7d9240c277
commit
9c8a5005f4
2 changed files with 8 additions and 2 deletions
|
|
@ -348,7 +348,8 @@ Working rule:
|
|||
- the compact opcode-`8` frontier therefore shifts:
|
||||
direct disassembly of `0x00430270` now shows that the add-building consumer does not branch on
|
||||
grouped opcode at all for descriptor strip `503..613`; it consumes the descriptor-derived
|
||||
candidate id, placement count byte `0x11`, and the packed span words at `0x14/0x16`.
|
||||
candidate id, placement count byte `0x11`, center words `0x12/0x14`, and radius word `0x16`,
|
||||
clamps that radius to at least `1`, and retries randomized placements up to `200` times.
|
||||
The next static-analysis pass should therefore target the remaining span-field meaning and
|
||||
shell-owned placement-flow ownership on that strip, not more missing-label recovery: the
|
||||
descriptor-side candidate bridge is now checked in across `503..613`, and the honest remaining
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue