parse constants from lea instruction as both number and offset features
See original GitHub issuewe often see the lea
instruction used for arithmetic e.g.
lea eax, [eax+61C88647h]
where in the above example 0x61C88647
is a magic value used in the tiny encryption algorithm (TEA).
Currently we parse 0x61C88647
as an offset
feature but ideally we would also parse the value as a number
feature to allow more concise rule writing. Parsing as both offset
and number
features would only apply to lea
instructions.
Pros:
- more concise rules for situations where
lea
is used for arithmetic
Cons:
- we potentially generate many additional
number
features
Issue Analytics
- State:
- Created a year ago
- Comments:5
Top Results From Across the Web
What's the purpose of the LEA instruction? - Stack Overflow
LEA , the only instruction that performs memory addressing calculations but doesn't actually address memory. LEA accepts a standard memory addressing operand, ...
Read more >Using the LEA instruction for arbitrary arithmetic
We have no constant offset in this example, so that has been left out. rsi : This is the register used for index...
Read more >What is the difference between LEA and MOV offset instruction ...
The simplest way to think of it is that MOV deals with data, whereas LEA deals with addresses. Both instructions are similar in...
Read more >Midterm 2 Review LC-3
Example: LDR R1, R4, #1. R1 is loaded from address pointed by R4 with offset 1. Store instructions use the same addressing modes,...
Read more >18. The OFFSET Operator and LEA Instruction - C-Jump
The OFFSET Operator and LEA Instruction. An address constant is a special type of immediate operand that consists of an offset or segment...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
dup of #320 😄
e.g.