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
*	4744	Kartik Agaram	2018-11-17	1	-2/+2
\|
*	4729	Kartik Agaram	2018-10-28	1	-2/+2
\| \| \| \| \| \|	Start injecting all dependencies in the Crenshaw compiler app. In the process I realized the non-fake code path of 'stop' had a bug.
*	4727 - commit to better 64-bit support	Kartik Agaram	2018-10-27	1	-15/+14
\| \| \| \| \| \| \|	I've started testing more regularly on 64-bit Linux, and I realize that the binaries actually now compare identical even on 64-bit. Why did I ever add that condition to CI? Seems to be working now on Travis. Let's start comparing now and see if the problem happens again.
*	4684	Kartik Agaram	2018-10-11	1	-1/+7
\| \| \| \| \| \| \| \| \| \|	Turns out the tests for 'trace' have been broken in native mode since the original commit (4674). Dangers of running my tests on Darwin, where I can't run them natively. The test failures didn't get flagged on CI because I'd forgotten to update the exit code of the factorial app in commit 4664. At least that's fixed in this commit.
*	4664 - subx: reflect test failures in exit status	Kartik Agaram	2018-10-05	1	-13/+5
\|
*	4648	Kartik Agaram	2018-10-01	1	-0/+8
\|
*	4647 - support 64-bit Linux in CI	Kartik Agaram	2018-10-01	1	-0/+148
	Generated 32-bit binaries are different on 64-bit. So let's compare them only on a 32-bit platform. And let's start also verifying their run-time behavior on Linux.