| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Use size-specific MAX/MIN constants | Maxwell Bernstein | 2020-10-22 | 1 | -2/+2 |
| | | | | | Don't rely on platform sizes. | ||||
| * | 7089 | Kartik Agaram | 2020-10-22 | 1 | -13/+16 |
| | | |||||
| * | 6912 | Kartik Agaram | 2020-09-30 | 1 | -6/+6 |
| | | |||||
| * | 6090 - new instruction: multiply by immediate | Kartik Agaram | 2020-03-06 | 1 | -3/+1 |
| | | | | | | | | | | | | | | | | This is a 3-operand instruction: r32 = rm32 * imm32 It looks like https://c9x.me/x86/html/file_module_x86_id_138.html has a bug, implying the same opcode supports a 2-operand version. I don't see that in the Intel manual pdf, or at alternative sites like https://www.felixcloutier.com/x86/imul Native runs seem to validate my understanding. In the process I also fixed a bug in the existing multiply instruction 0f af: the only flags it sets are OF and CF. The other existing multiply instruction f7 was doing things right. | ||||
| * | 5983 - fix an emulator bounds-check bug | Kartik Agaram | 2020-02-05 | 1 | -1/+1 |
| | | | | | | | It was possible for an instruction to write out of bounds of the memory data structure. Most of the time this worked fine. However if the block ever got resized and moved the out-of-bounds bytes no longer went along. | ||||
| * | 5818 | Kartik Agaram | 2019-12-22 | 1 | -1/+1 |
| | | |||||
| * | 5485 - promote SubX to top-level | Kartik Agaram | 2019-07-27 | 1 | -0/+1279 |