| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
https://stackoverflow.com/questions/1815329/portable-way-to-get-file-size-in-bytes-in-the-shell/1815582#1815582
|
|
|
|
| |
Many thanks again, Wade.
|
| |
|
| |
|
|
|
|
|
| |
This typo has been around since July 2019 (commit 784e17d487). I swear
I've spelt the name correctly scores of times before that.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I spent some time timing this command:
cd ./linux/bootstrap; ./clean; popd; time ./translate_emulated apps/ex2.mu
Times at a few commits this year, along with notes on what changed in the
linux/ directory:
517a01c95a62a8d6227357d514dc9fff83388153 Feb 17 1:30
time ./translate_mu_baremetal_emulated baremetal/ex2.mu
71e4f3812982dba2efb471283d310224e8db363e Mar 3 1:30
time ./translate_emulated ex2.mu
2df1d1a73046a0a7b6523552b53f407651ed36df May 14 1:53
time ./translate_emulated apps/ex2.mu
ff8ec9bcff7577ba923fe7868ea62ecceed55ee7 + patch May 14 2:10 -- start showing stack trace on abort
9831a8cef9cb8f412590ffa6ab9f52b8b51ab9d2 + patch May 19 2:23
8c47da082b63b6aa6aafd45e1f8f7edd4459e555 Jun 18 2:27
-- what changed in the middle here?!
b625c6304eca827c04eda719fa6f7927294b80bc Jul 29 3:13
-- seemingly minor change to linux/next-word
52e3ea8a4bec791e4c2d64fb8aca9e26cdf60f25 Aug 15 4:55
ba4a3c5be70d473479e663be0400b798f88c113d Aug 22 4:57
-- one additional compiler check in linux/mu.subx
899cdcc3f3da2be04801ab79b53ec2264e8b1e4c Aug 29 5:44 5:54
975f372d67a5242d3c046712d43ec9f61a920009 Oct 31 5:22
So it's not a single commit :/ Unclear what's going on.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Thanks Sumeet Agarwal for the suggestion.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Snapshot. Keyboard interrupt being triggered.
This was hard to debug until https://stackoverflow.com/questions/37618111/keyboard-irq-within-an-x86-kernel
reminded me that I'd forgotten to enable IRQ1 on port 0x21.
For a while I was confused by never hitting a breakpoint at the start of
the keyboard handler. Then I found https://sourceforge.net/p/bochs/discussion/39592/thread/5e397455
and started skipping one instruction in my breakpoint.
I still don't understand the discrepancy between some people installing
the handler at entry 9, and others installing at entry 0x21 = 33.
|