| Age | Commit message (Collapse) | Author |
|---|
|
This makes it easier to see which instructions still need to be lifted
versus those which never should be lifted.
|
|
These aren't really needed; if it's for a 32-bit architecture that can't
handle 64-bit shifts, then the instruction won't be decoded in the first
place. Because the registerSize is derived from the address size, it may
interfere with 64-bit architectures that are using signed 32-bit
addresses.
There are a few other places that check registerSize (for example, the
32->64 bit sign extension idiom and MADD, MADDU) that are suspect, but
not included in this commit. The difference is that for 64-bit shifts,
checking at all for the register size is the problem; for those, the
check is still needed to figure out whether to sign extend or not, but
the value of registerSize is suspect.
|
|
Closes #5403.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
https://github.com/Vector35/binaryninja-api/issues/5815
|
|
https://github.com/Vector35/binaryninja-api/issues/4028
|
|
represent a C char
|
|
|
|
More info: https://doc.rust-lang.org/cargo/reference/manifest.html#the-rust-version-field
|
|
|
|
Solution was added in the core
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For debugging threads when you have like 50 and want to find one at a glance
|
|
|
|
|
|
A user reported in public slack that the definition doesn't agree on
endianness
|
|
|
|
|
|
external linking"
This reverts commit 8b410e9129c74476c369e7870121e980fa4cc1d1.
|
|
|
|
|
|
|
