laie

ps) currently I am testing a version that ZydisEncoder takes "intended_max_size" for an operand. along with original size estimation, cap the size with this intended_max_size value it resolves all issues...

Thanks! I am working around with several methods. But it gives me quite afraid. Say I specially treat "rotl"'s imm as "unsigned" and others as "signed", it feels like it...

thanks! it clarified and helped a lot!

well even "max possible size" of certain mnemonic, as database, not going to be easy? for example Jmp Imm has (I presume) 5 bytes max. I am writing a recompiler....

Feature Proposal: Maximum Instruction Size Lookup for ZydisEncoder First, I want to express my appreciation for Zydis. The library's exceptional code quality has saved us significant development time, and its...

For example: Jmp, Imm -> 5 bytes Jmp, Mem -> I don’t know but will be much less than 15 bytes Call imm -> 5 bytes … I gave up...

```markdown Thank you for the attention. Let me provide more materialized example case: ## Core Problem Visualization ```nasm Block0: push reg1 push reg2 sub rsp, const1 ; size uncertainty jmp...

Still want to argue this feature would be valuable: 1. My UnrealEngine4 sample has 12,465,412 instructions, for example. Real world samples often exceed 1,000,000 by far margin. 2. Key point...

Let me separate the concerns and proposal: 1. In the ZydisDecoder, I propose adding a dedicated REL_IMM operand type while removing the 'is_relative' flag from IMM operands. Because: - REL_IMM...