Skip to content

feat: impl. cluster shuffle transform#139

Draft
g4titanx wants to merge 6 commits intomasterfrom
feat/cluster-shuffle
Draft

feat: impl. cluster shuffle transform#139
g4titanx wants to merge 6 commits intomasterfrom
feat/cluster-shuffle

Conversation

@g4titanx
Copy link
Member

@g4titanx g4titanx commented Mar 6, 2026

No description provided.

@g4titanx g4titanx changed the base branch from master to fix/push_split-invalid-jumps March 6, 2026 09:26
@g4titanx
Copy link
Member Author

g4titanx commented Mar 6, 2026

the issue right now is the interaction between FunctionDispatcher and ClusterShuffle specifically. FunctionDispatcher creates blocks with raw PUSH imm. (BlockControl::Unknown/Terminal), not symbolic JumpTarget::Block targets. so when ClusterShuffle moves blocks afterward, those raw PUSH values become stale. the entire patch re-application machinery (dispatcher patches, stub patches, decoy patches, controller patches, min_push_width, remap_metadata_pcs, pre_reindex_pc_mapping composition) exists to fix up those stale values and it's still producing ~21-25 invalid jump targets.

but what if ClusterShuffle runs first, FunctionDispatcher writes its raw PUSH values against the already-shuffled layout, and they're correct from the start. no re-application needed. attempting this approach

Base automatically changed from fix/push_split-invalid-jumps to master March 12, 2026 10:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant