Soul of a tiny new machine. More thorough tests → More comprehensible and rewrite-friendly software → More resilient society. https://git.tilde.institute/akkartik/mu/atom?h=main 2021-03-04T06:21:03Z 2021-03-04T06:21:03Z Kartik K. Agaram vc@akkartik.com 2021-03-04T06:09:50Z urn:sha1:71e4f3812982dba2efb471283d310224e8db363e 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. 2020-12-25T20:28:10Z Kartik Agaram vc@akkartik.com 2020-12-25T20:26:05Z urn:sha1:47287fbf1af21207d8f847842fb32db9ee95e4c8 2020-05-25T05:57:07Z Kartik Agaram vc@akkartik.com 2020-05-25T05:56:08Z urn:sha1:f4e609c3a7beb0e900cd28102dd9f226f9e5c437 Stay silent if all is well. I don't agree with this, but it's not like the messages I was printing out were particularly useful. 2020-01-02T10:01:41Z Kartik Agaram vc@akkartik.com 2020-01-02T09:41:55Z urn:sha1:9e5e87ca3776efa5f0d772ed8cf348bf6ee4d08e Give the bootstrap C++ program a less salient name. 2020-01-02T00:45:30Z Kartik Agaram vc@akkartik.com 2020-01-02T00:45:30Z urn:sha1:23fd294d85959c6b476bcdc35ed6ad508cc99b8f Rename a few scripts to be more consistent. I'm also starting to feel the urge to bud off `subx run` into its own program, say tools/emulate_x86. It doesn't really rely on the SubX notation at all. And then I could rename `subx translate` to `translate_subx_bootstrap`. Only problem: the commands in the Readme get verbose. But the Readme is gonna need surgery soon anyway to put translate_mu front and center.