mu - Soul of a tiny new machine. More thorough tests → More comprehensible and rewrite-friendly software → More resilient society.

	Commit message (Collapse)	Author	Age	Files	Lines
*	support checking overflow flag everywhere	Kartik K. Agaram	2021-05-08	1	-9/+239
\|
*	always check for null in 'index' instructions	Kartik K. Agaram	2021-05-07	1	-86/+112
\|
*	always check for null in 'get' instructions	Kartik K. Agaram	2021-05-07	1	-13/+35
\|
*	opt: don't clear streams of bytes on the stack	Kartik K. Agaram	2021-04-21	1	-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 traces	Kartik K. Agaram	2021-04-20	1	-0/+1
\|
*	.	Kartik Agaram	2021-03-29	1	-1/+1
\|
*	7867	Kartik K. Agaram	2021-03-07	1	-235/+235
\|
*	7842 - new directory organization	Kartik K. Agaram	2021-03-03	1	-0/+38350
	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.