about summary refs log tree commit diff stats
path: root/015immediate_addressing.cc
Commit message (Collapse)AuthorAgeFilesLines
* 7842 - new directory organizationKartik K. Agaram2021-03-031-1311/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Baremetal is now the default build target and therefore has its sources at the top-level. Baremetal programs build using the phase-2 Mu toolchain that requires a Linux kernel. This phase-2 codebase which used to be at the top-level is now under the linux/ directory. Finally, the phase-2 toolchain, while self-hosting, has a way to bootstrap from a C implementation, which is now stored in linux/bootstrap. The bootstrap C implementation uses some literate programming tools that are now in linux/bootstrap/tools. So the whole thing has gotten inverted. Each directory should build one artifact and include the main sources (along with standard library). Tools used for building it are relegated to sub-directories, even though those tools are often useful in their own right, and have had lots of interesting programs written using them. A couple of things have gotten dropped in this process: - I had old ways to run on just a Linux kernel, or with a Soso kernel. No more. - I had some old tooling for running a single test at the cursor. I haven't used that lately. Maybe I'll bring it back one day. The reorg isn't done yet. Still to do: - redo documentation everywhere. All the README files, all other markdown, particularly vocabulary.md. - clean up how-to-run comments at the start of programs everywhere - rethink what to do with the html/ directory. Do we even want to keep supporting it? In spite of these shortcomings, all the scripts at the top-level, linux/ and linux/bootstrap are working. The names of the scripts also feel reasonable. This is a good milestone to take stock at.
* 7133Kartik Agaram2020-10-281-2/+2
|
* .Kartik Agaram2020-10-241-3/+3
|
* bootstrap: more tweaks to int constantsKartik Agaram2020-10-231-13/+13
|
* 7089Kartik Agaram2020-10-221-18/+18
|
* 7041Kartik Agaram2020-10-151-12/+12
| | | | Reconcile a few details with the mu-normie fork.
* 6090 - new instruction: multiply by immediateKartik Agaram2020-03-061-0/+39
| | | | | | | | | | | | | | | 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 bugKartik Agaram2020-02-051-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.
* 5818Kartik Agaram2019-12-221-3/+3
|
* 5713Kartik Agaram2019-10-231-2/+2
|
* 5485 - promote SubX to top-levelKartik Agaram2019-07-271-0/+1272