about summary refs log tree commit diff stats
path: root/014indirect_addressing.cc
Commit message (Collapse)AuthorAgeFilesLines
* 7842 - new directory organizationKartik K. Agaram2021-03-031-1005/+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.
* .Kartik Agaram2020-10-241-8/+8
|
* Use size-specific MAX/MIN constantsMaxwell Bernstein2020-10-221-1/+1
| | | | Don't rely on platform sizes.
* 7089Kartik Agaram2020-10-221-24/+24
|
* 7041Kartik Agaram2020-10-151-29/+29
| | | | Reconcile a few details with the mu-normie fork.
* 6924Kartik Agaram2020-10-011-10/+10
|
* 6914Kartik Agaram2020-09-301-13/+13
|
* 6912Kartik Agaram2020-09-301-6/+6
|
* 6911 - comparing floatsKartik Agaram2020-09-301-6/+6
| | | | | | | It turns out floating-point operations set different flags than most instructions. We have to branch on them using unsigned jumps. https://stackoverflow.com/questions/7057501/x86-assembler-floating-point-compare/7057771#7057771
* 6760Kartik Agaram2020-09-081-2/+7
| | | | | | | | Fix a couple of subtle bugs. - the VM was conditionally reading from the instruction stream, so that other bugs got masked by decoding errors. - push-n-bytes was clobbering eax.
* 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-10/+10
|
* 5485 - promote SubX to top-levelKartik Agaram2019-07-271-0/+1000