| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2024-04-02 | lets see how a visitor for operands works out here... | iximeow | |
| 2024-04-02 | display: gate rep printing with a simpler check | iximeow | |
| testing against six opcodes to see if we should print rep or repnz is a bit absurd. they are relatively rare instructions, so this is a long sequence of never-taken tests. we can avoid the whole thing in the common case by testing if there is any kind of rep prefix at all. | |||
| 2024-04-02 | swap test order for segment override applicability | iximeow | |
| it is almost always the case that self.prefixes.segment == Segment::DS, meaning testing for it first avoids checking `self.operands[op].is_memory()` later. this overall avoids a few instructions in the typical path, rather than checking `is_memory()` first (which would always be true in the places this function is called from) | |||
| 2024-04-02 | display opt: mem size labels and minor segment reporting changes | iximeow | |
| for mem size labels: add one new "BUG" entry at the start of the array so `mem_size` does not need to be adjusted before being used to look up a string from the `MEM_SIZE_STRINGS` array. it's hard to measure the direct benefit of this, but it shrinks codegen size by a bit and simplfies a bit of assembly.... for segment reporting changes: stos/scas/lods do not actually need special segment override logic. instead, set their use of `es` when decoded, if appropriate. this is potentially ambiguous; in non-64bit modes the sequence `26aa` would decode as `stos` with explicit `es` prefix. this is now identical to simply decoding `aa`, which now also reports that there is an explicit `es` prefix even though there is no prefix on tne instruction. on the other hand, the prefix-reported segment now more accurately describes the memory selector through which memory accesses will happen. seems ok? | |||
| 2024-04-02 | correctly label fmt benchmark metrics | iximeow | |
| 2024-04-02 | the name for instructions and cycles metrics from perf vary by kernel version | iximeow | |
| on midgard there is no :u suffix, so try both | |||
| 2024-04-01 | add perf testing to mainline goodfile | iximeow | |
| 2023-12-16 | version bump for 1.2.21.2.2 | iximeow | |
| 2023-12-16 | fix hreset being disassembled as having second operand of "Nothing" | iximeow | |
| just report it having one operand... | |||
| 2023-12-16 | fix incorrect register class names in long_mode1.2.1 | iximeow | |
| also adjust changelog for a 1.2.1 version again, no new interfaces to go with these bugfixes. | |||
| 2023-12-16 | fix incorrect register selection for `vpbroadcastm{b2q,w2d}` with `rex.b` set | iximeow | |
| 2023-12-16 | fix incorrect register selection for `vpmov*2m` with `rex.r` set | iximeow | |
| 2023-12-16 | fix incorrect register selection for `vpmovm2*` with `rex.b` set | iximeow | |
| 2023-12-16 | abnormal memory sizes for keylocker instructions are not bugs | iximeow | |
| new `does_not_decode_invalid_registers` fuzzer found other bugs! the 384-bit accesses for 128b keylocker instructions are an otherwise-unknown size and had a memory size of `BUG`. they are not bugs. give the memory size a real name. | |||
| 2023-12-16 | reword new changelog entries | iximeow | |
| 2023-12-16 | fix opportunity for unhandled register synonyms | iximeow | |
| registers `al`, `cl`, `dl`, and `bl` could have two different representations - with `rex.w` and without. these two forms of `RegSpec` would not compare equal, nor has the same, so for code relying on `RegSpec` to faithfully represent a 1-1 mapping to x86 registers, these synonyms would introduce bugs in register analysis. for example, in `yaxpeax-core`, this would result in instructions writing to `rex.w al` not being visible as definitions for a future read of `!rex.w al`. fix this in `x86_64` code, add new test cases about the confusion, adjust register names to make this situation more clearly a bug, and introduce two new fuzz targets that would have helped spot this error. | |||
| 2023-12-15 | update changelog, bump version number for future publish | iximeow | |
| 2023-12-15 | more RegSpec constructor validation, fix bug in x86_64 1b reg specs | iximeow | |
| * the first four 1-byte registers, `al`, `cl`, `dl`, `bl`, can be constructed in two ways that produce "identical" `RegSpec` that are.. not. e.g. `RegSpec::al() != Regspec::rb(0)` even though `RegSpec::al().name() == RegSpec::rb(0).name()`. this corrects the `rb` constructor at least, but instructions like `4830c0` and `30c0` still produce incompatible versions of `al`. * also fix register numbering used explicit qword-sized RegSpec constructors, r12 and r13 used to produce r8 and r9 | |||
| 2023-12-15 | fix incorrect register numbers in r12/r13 RegSpec constructor functions | Dongjia "toka" Zhang | |
| these functions had a copypaste error where the r12 and r13 versions would create RegSpec for registers 8 and 9 instead of 12 and 13. use correct register numbers in these macros. | |||
| 2023-07-24 | 1.2.0 (Cargo.toml this time)1.2.0 | iximeow | |
| 2023-07-24 | 1.2.0 | iximeow | |
| 2023-07-24 | fix handling of lar/lsl source register | iximeow | |
| 2023-07-23 | fix inconsistently-poreted memory access size of vcvt{,t}{sd,si} | iximeow | |
| 2023-07-23 | fix + better test cvttsd2si+cvtsd2si (misdecode under 64-bit) | iximeow | |
| 2023-07-16 | a few notes before calling this [somewhat substantial] refactor done | iximeow | |
| 2023-07-16 | forward changes along to 16-bit decoder... | iximeow | |
| 2023-07-16 | fix indentation | iximeow | |
| 2023-07-16 | unify 64-/32-bit more | iximeow | |
| 2023-07-16 | forward changes along to 32-bit decoder... | iximeow | |
| 2023-07-09 | re-enable tests, pretty sure ive squeezed out as much opt as im getting ↵ | iximeow | |
| right now... | |||
| 2023-07-09 | trying to delete branches on bank size | iximeow | |
| 2023-07-09 | more matches to be mad at and turn into lookups instead | iximeow | |
| 2023-07-09 | irritated at matches | iximeow | |
| 2023-07-09 | that doesnt need to be a transmute | iximeow | |
| 2023-07-09 | changing OpcodeRecord to avoid bad use of simd | iximeow | |
| 2023-07-09 | smaller tables and err variants preserves perf, but less code/data | iximeow | |
| 2023-07-09 | table-izing these matches substantially helps (pending bugs...) | iximeow | |
| 2023-07-09 | remove very done todo | iximeow | |
| 2023-07-09 | bitpacking is_memory seems to help (surpisingly much!) | iximeow | |
| 2023-07-09 | Revert "restructuring of hotpath code, not worse but not better" | iximeow | |
| This reverts commit 15c821a2d3fbf2fc0458090b6cc12f2ac093f075. | |||
| 2023-07-09 | restructuring of hotpath code, not worse but not better | iximeow | |
| 2023-07-08 | consistently report end of prefixes/start of opcode | iximeow | |
| 2023-07-08 | todo for 2.x | iximeow | |
| 2023-07-08 | seems like this makes things a bit faster...? | iximeow | |
| 2023-07-08 | move rip-rel check to a slightly colder spot... | iximeow | |
| 2023-07-08 | annotation ordering changed a bit in refactoring, for the better??? | iximeow | |
| 2023-07-08 | actually reject lock prefixes in vex instructions | iximeow | |
| 2023-07-08 | fix v(p)gather situations, get vex tests passing again | iximeow | |
| 2023-07-06 | defer assigning mem_size or operand_count too | iximeow | |
| 2023-07-06 | M_Gv should be unreachable too... | iximeow | |
 |
index : yaxpeax-x86 | |
| yaxpeax x86 decoder |
| aboutsummaryrefslogtreecommitdiff |