about summary refs log tree commit diff stats
path: root/linux
Commit message (Collapse)AuthorAgeFilesLines
* opt: don't clear streams of bytes on the stackKartik K. Agaram2021-04-212-3/+152
| | | | | | | | | | | | All over the Mu code I reflexively initialize all variables just to keep unsafe SubX easy to debug. However I don't really need to do this for safe Mu code, since the type- and memory-safety already ensures we can't read from streams beyond what we've written to them. For now I'll continue mostly with the same approach, but with one exception for streams of bytes. Mu programs often emit traces, and in doing so they often use temporary streams of bytes that can get quite long. I'm hoping avoiding initializing KBs of data all over the place will measurably speed up the Mu shell.
* an interface approximating stack tracesKartik K. Agaram2021-04-202-0/+1
|
* undo previous commitKartik K. Agaram2021-04-052-3/+1
|
* snapshot: stupid debugging sessionKartik K. Agaram2021-04-052-1/+3
| | | | | | | | | | | | | | | I spent a while building a little keyboard scancode printer: $ ./translate ex1.mu && qemu-system-i386 disk.img ..and wondering why up-arrow was 0x48 in hex but 724 in decimal. I ended up paranoidly poking at a bunch of crap (though there _is_ a cool chromatography-based debugging technique in 126write-int-decimal.subx) before I realized: - 724 just has one extra digit over the correct answer - the 0xe0 scan code is a 3-digit number in decimal -- and the final digit is '4' There's nothing actually wrong.
* .Kartik Agaram2021-04-041-7/+9
|
* make online help more obviousKartik Agaram2021-04-041-0/+4
|
* some hacky checks for common errorsKartik K. Agaram2021-03-311-0/+4
| | | | | They're not really baked into the regular compilation process; I have to remember to run them if I see strange behavior.
* .Kartik Agaram2021-03-2938-98/+98
|
* .Kartik K. Agaram2021-03-261-0/+115
|
* .Kartik Agaram2021-03-241-0/+636
|
* fix a failing test in pack.subxKartik K. Agaram2021-03-152-5/+68
|
* boot.subx is now clean SubXKartik K. Agaram2021-03-152-1/+27
|
* .Kartik K. Agaram2021-03-152-16/+63
|
* .Kartik K. Agaram2021-03-146-31/+28
|
* .Kartik K. Agaram2021-03-142-1/+28
|
* treat boot.hex as a SubX fileKartik K. Agaram2021-03-142-45/+45
|
* survey_baremetal: padding between segmentsKartik K. Agaram2021-03-142-10/+552
| | | | Optional.
* survey_baremetal: support /imm8Kartik K. Agaram2021-03-142-2/+14
|
* survey: document starting address of each segmentKartik K. Agaram2021-03-142-15/+80
|
* some cleanup in a translation phaseKartik K. Agaram2021-03-134-30/+31
|
* .Kartik Agaram2021-03-121-0/+4
|
* some tweaks while updating mu-normieKartik Agaram2021-03-123-4/+6
|
* .Kartik K. Agaram2021-03-092-17/+18
|
* make the library reference easier to findKartik K. Agaram2021-03-091-1/+2
|
* .Kartik K. Agaram2021-03-091-35/+14
|
* update vocabulary documentationKartik K. Agaram2021-03-085-11/+383
| | | | Top-level and linux/ now have separate vocabulary.md files.
* .Kartik K. Agaram2021-03-083-12/+18
|
* 7867Kartik K. Agaram2021-03-0735-554/+554
|
* 7847Kartik K. Agaram2021-03-0431-75/+75
|
* 7846Kartik K. Agaram2021-03-0428-37/+32
|
* 7843 - clean up README after directory reorgKartik K. Agaram2021-03-034-15/+160
|
* 7842 - new directory organizationKartik K. Agaram2021-03-03229-0/+425626
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.