Skip to content

Standardize the values for invalid and data opcodes#261

Merged
encounter merged 2 commits into
encounter:mainfrom
ethteck:standard-invalid-opcode
Sep 13, 2025
Merged

Standardize the values for invalid and data opcodes#261
encounter merged 2 commits into
encounter:mainfrom
ethteck:standard-invalid-opcode

Conversation

@ethteck

@ethteck ethteck commented Sep 13, 2025

Copy link
Copy Markdown
Contributor

This makes it so that all arches share the same value for an invalid opcode, so platform-specific logic isn't needed for checking whether instructions are valid.

Also updated dependencies

>
> This makes it so that all arches share the same value for an invalid opcode, so platform-specific logic isn't needed for checking whether instructions are valid.
Also updated dependencies
@ethteck ethteck force-pushed the standard-invalid-opcode branch from 1fb5b31 to 3b718e3 Compare September 13, 2025 08:41
@encounter

Copy link
Copy Markdown
Owner

It seems we’re conflating the concept of "invalid" and "data" opcodes. I’d prefer to make OPCODE_INVALID u16::MAX. Then OPCODE_DATA can be u16::MAX - 1.

@ethteck

ethteck commented Sep 13, 2025

Copy link
Copy Markdown
Contributor Author

okay, sounds good

Comment thread objdiff-core/src/arch/arm.rs
@encounter encounter changed the title Standardize the value for an invalid opcode Standardize the values for invalid and data opcodes Sep 13, 2025
@encounter

Copy link
Copy Markdown
Owner

Looks great, thanks!

@encounter encounter merged commit e2c7034 into encounter:main Sep 13, 2025
24 checks passed
@ethteck ethteck deleted the standard-invalid-opcode branch September 13, 2025 18:39
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.

2 participants