Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | shell: ctrl-r runs on real screen without a trace | Kartik K. Agaram | 2021-04-17 | 1 | -1/+1 |
| | | | | | We run out of memory fairly early in the course of drawing a chessboard on the whole screen. | ||||
* | . | Kartik K. Agaram | 2021-04-16 | 1 | -3/+3 |
| | |||||
* | rename boot.hex to boot.subx | Kartik K. Agaram | 2021-03-14 | 1 | -1/+1 |
| | |||||
* | treat boot.hex as a SubX file | Kartik K. Agaram | 2021-03-14 | 1 | -6/+4 |
| | |||||
* | 7842 - new directory organization | Kartik K. Agaram | 2021-03-03 | 1 | -26/+29 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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. | ||||
* | 7440 | Kartik Agaram | 2020-12-28 | 1 | -9/+9 |
| | |||||
* | 7439 - start translating Mu programs to baremetal | Kartik Agaram | 2020-12-28 | 1 | -1/+1 |
| | |||||
* | 7401 - clean up support for non-Linux platforms | Kartik Agaram | 2020-12-25 | 1 | -15/+2 |
| | |||||
* | 7400 | Kartik Agaram | 2020-12-25 | 1 | -3/+0 |
| | | | | | Turns out the default 8MB stack is quite enough for the programs I'm currently running. | ||||
* | 6527 - increase stack limits | Kartik Agaram | 2020-06-15 | 1 | -0/+3 |
| | | | | | | We haven't run into this limit yet, but everytime I see a 'stream overflow' error I run into it while going over all the knobs in apps/subx-params.subx, if I increase Input-size (used by survey.subx) too much. | ||||
* | core translator phases now emit identical binaries | Kartik Agaram | 2020-05-18 | 1 | -1/+1 |
| | |||||
* | fix a crash when translating apps/ex1 | Kartik Agaram | 2020-05-18 | 1 | -1/+1 |
| | |||||
* | 5851 | Kartik Agaram | 2020-01-01 | 1 | -0/+53 |
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. |