aboutsummaryrefslogtreecommitdiff
path: root/src/real_mode/mod.rs
diff options
context:
space:
mode:
authoriximeow <me@iximeow.net>2021-08-21 13:21:50 -0700
committeriximeow <me@iximeow.net>2021-08-21 13:21:50 -0700
commite4131e4eb64595d9b24493eb31a9af4c5e21b1eb (patch)
tree23b0eee34ff593948b7ef012bd61a68bce0e1feb /src/real_mode/mod.rs
parent9687a5af1d712da41992cba8d241ddef8bdc50ec (diff)
add push/pop/call/ret mem_size fixes to changelog
Diffstat (limited to 'src/real_mode/mod.rs')
-rw-r--r--src/real_mode/mod.rs5
1 files changed, 2 insertions, 3 deletions
diff --git a/src/real_mode/mod.rs b/src/real_mode/mod.rs
index 8a7e453..7f3ad42 100644
--- a/src/real_mode/mod.rs
+++ b/src/real_mode/mod.rs
@@ -4229,9 +4229,8 @@ impl Instruction {
/// the reported size is correct for displayed operand sizes (`word [ptr]` will have a
/// `MemoryAccessSize` indicating two bytes) but is _not_ sufficient to describe all accesses
/// of all instructions. the most notable exception is for operand-size-prefixed `call`, where
- /// `66ff10` is the instruction `call dword [eax]`, but will push a four-byte `eip`. this same
- /// imprecision exists for `jmp dword [mem]` as well. tools must account for these inconsistent
- /// sizes internally.
+ /// `66ff10` is the instruction `call dword [eax]`, but will push a four-byte `eip`. tools
+ /// must account for these inconsistent sizes internally.
pub fn mem_size(&self) -> Option<MemoryAccessSize> {
if self.mem_size != 0 {
Some(MemoryAccessSize { size: self.mem_size })