Repository navigation
Preserve decoded operand order for semantic instruction comparisons - #5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Register-to-segment MOV instructions render with reversed operands in the historical Ghidra export profile. Add an opt-in decoded operand order to render_body so semantic comparisons show
8E C0asMOV ES, AX, while preserving prefix handling, implied shift counts and the existing export default.Validation: 258 pytest tests passed, 34 existing skips. Fifteen new cases cover segment moves, memory forms, exchange ordering, segment and REP prefixes and implied shift counts. Fourteen opcode fixtures were compared locally with native NASM 3.02 ndisasm. No decoder or TPU changes.