about summary refs log tree commit diff stats
path: root/translate_subx_baremetal
Commit message (Collapse)AuthorAgeFilesLines
* 7748Kartik K. Agaram2021-02-151-1/+1
| | | | | | | | Bug in code-size check. It costs 18 bytes in the boot sector to load 2 tracks of disk (63KB). At that rate I can load 6 more tracks before I need to perform the drudgery again of recalculating offsets.
* 7720 - baremetal: load more sectors againKartik K. Agaram2021-02-111-1/+1
|
* 7556Kartik Agaram2021-01-241-1/+1
|
* 7547 - baremetal: rpn calculatorKartik Agaram2021-01-221-1/+1
| | | | | | | | Still in progress. Known bugs: * Cursor management is broken. Every line currently seems to leave behind a shadow cursor. * No shift-key support yet, which means no addition or multiplication. (This app doesn't have division yet.)
* 7546 - baremetal: disk size checkKartik Agaram2021-01-221-0/+6
|
* 7523Kartik Agaram2021-01-151-0/+3
| | | | | | | | | | | | | | | | | | | | There's a dependency cycle here: - draw-grapheme (Mu) uses read-grapheme (Mu) to be unicode-aware. - read-grapheme uses read-byte (SubX). Streams are a fundamental data structure in Mu. For the Mu compiler to be able to reason about the safety of stream operations, they need to be an opaque type. All stream primitives are written in SubX. To manipulate a stream's internals we force people to reach for SubX. That way if there's no SubX code there's confidence that things are safe. - read-byte and other stream operations have unit tests, like they should. The unit tests need to print data to screen when say a test fails. To do this they use various check- functions (SubX) that take a string argument. - Printing a string to screen uses draw-grapheme (Mu). Perhaps I should maintain variants of drawing primitives that operate only on ASCII.
* 7522 - bring back a few tests in .subx filesKartik Agaram2021-01-151-0/+6
| | | | | | | | Even though baremetal has tests in SubX, they can only run in Mu programs since the test harness is currently in a Mu layer. Baremetal isn't really intended for running SubX programs at the moment. Is this a step down the slippery slope towards C compilers that I complained about in http://akkartik.name/akkartik-convivial-20200607.pdf?
* 7463Kartik Agaram2020-12-291-3/+2
|
* 7461Kartik Agaram2020-12-291-0/+6
|
* 7460 - baremetal backend for SubXKartik Agaram2020-12-291-0/+26