yaxpeax-x86/test/protected_mode, branch 1.1.4 yaxpeax x86 decoder fuzz DisplayStyle::C and fix corresponding issues 2022-01-12T23:46:39+00:00 iximeow me@iximeow.net 2022-01-12T23:46:39+00:00 e80b5622ec956a92f24ce6487fb0d76e9c541515 






fix incorrect memory size for f30f1e-style nop
2021-12-19T19:23:18+00:00

iximeow
me@iximeow.net

2021-12-19T19:23:18+00:00

e7dec7baa9c6649d71e1b349d93dce6b0cd588bf

not only did the instruction have wrong data, but if displayed, the
formatter would panic.





not only did the instruction have wrong data, but if displayed, the
formatter would panic.







test that invalid RegSpec constructions panic as expected
2021-12-19T17:09:20+00:00

iximeow
me@iximeow.net

2021-12-19T17:06:12+00:00

d13d8ebfad98b3d547f455ec9d73dab98f0899c3

in the process, fix 64-bit rex-byte limit, 32/16-bit mode mask reg limit





in the process, fix 64-bit rex-byte limit, 32/16-bit mode mask reg limit







do not panic on negative compressed displacements, i mean it!!
2021-12-17T18:46:21+00:00

iximeow
me@iximeow.net

2021-12-17T18:45:31+00:00

2c332661b5ccf116a468e1e23711017d77c1531a












displacements are stored as unsigned, but are functionally signed ints
2021-12-17T04:01:26+00:00

iximeow
me@iximeow.net

2021-12-17T03:58:15+00:00

f063f747c21548329170fd09fd09d391b2277aed

so multiplying to expand EVEX compressed offsets can overflow, and that
needs to be okay.





so multiplying to expand EVEX compressed offsets can overflow, and that
needs to be okay.







support endbr{32,64}
2021-10-10T21:40:55+00:00

iximeow
me@iximeow.net

2021-10-10T21:40:55+00:00

ed5c76a0f8e92656539f305b9b7ea5e032517f36












fix negative relative branches (again!!! +- is bad!!!)
2021-08-21T21:33:13+00:00

iximeow
me@iximeow.net

2021-08-21T21:33:13+00:00

dff9a7e4a14984705db8fb18550af5a4fa9ce3d5












clarify inaccurate 32/16-bit `call/jmp [mem]` mem_size
2021-08-21T20:15:46+00:00

iximeow
me@iximeow.net

2021-08-21T20:13:26+00:00

9687a5af1d712da41992cba8d241ddef8bdc50ec












report memory sizes for push, pop, call, ret
2021-08-21T19:13:01+00:00

iximeow
me@iximeow.net

2021-08-21T19:13:01+00:00

cef4feeaf9c64e03a6728f267750ac2fb32eb9ff

these instructions had memory sizes reported for the operand, if it was
a memory operand, but for versions with non-memory operands the decoded
`Instruction` would imply that non memory access would happen at all.
now, decoded instructions in these cases will report a more useful
memory size.





these instructions had memory sizes reported for the operand, if it was
a memory operand, but for versions with non-memory operands the decoded
`Instruction` would imply that non memory access would happen at all.
now, decoded instructions in these cases will report a more useful
memory size.







relative branches should be shown as $+offset, not just plain offset
2021-08-14T07:48:02+00:00

iximeow
me@iximeow.net

2021-08-14T07:44:09+00:00

9bc4eca4b8269cb8e0898dfe05c3ed4059cf4fd5

while x86 branches of immediates are all relative to PC, other
architectures may have absolute branches to immediate addresses, leaving
this syntax ambiguous and potentially confusing. yaxpeax prefers to
write relative offsets `$+...` as a rule, so uphold that here.





while x86 branches of immediates are all relative to PC, other
architectures may have absolute branches to immediate addresses, leaving
this syntax ambiguous and potentially confusing. yaxpeax prefers to
write relative offsets `$+...` as a rule, so uphold that here.