duskos

dusk os fork
git clone git://git.alexwennerberg.com/duskos
Log | Files | Refs | README | LICENSE

commit 8791863df2db483942897cca9a71f299936c172b
parent b74b2f13def55aaab1e34b8f4027bb6283590312
Author: Virgil Dupras <hsoft@hardcoded.net>
Date:   Wed, 30 Nov 2022 08:06:45 -0500

Update README

Diffstat:
MREADME.md | 23+++++++++++++----------
Mfs/doc/design/simple.txt | 2+-
2 files changed, 14 insertions(+), 11 deletions(-)

diff --git a/README.md b/README.md @@ -142,11 +142,8 @@ higher cognitive space to fit BSD/Linux wider abstractions in your mind. * Has a VM written in C, buildable from a POSIX environment, which allows Dusk to build itself for any of its supported targets. -* Has an "almost C" compiler which still needs a lot of work, but is already - capable of compiling a nice subset of C. For example, it can compile Collapse - OS C VM and a ported version of [uxn][uxn]. You can see the kind of code that - Dusk is capable of compiling and executing at [fs/tests/comp/c/test.c][5] and - you can read about its [technical details][duskcc]. +* Has an ["almost C" compiler][duskcc] which still needs a lot of work, but is + already capable of compiling a nice subset of C. * It can run bare metal on some PCs (and QEMU, of course). It has drivers (in various state of sophistication) for: * VGA in text mode @@ -160,13 +157,19 @@ higher cognitive space to fit BSD/Linux wider abstractions in your mind. * Can create new FAT12 volumes. * It completely self-hosts on all its target (only PC for now) machines. +List of ported C codebases: + +* The CVM of [Collapse OS][collapseos] +* The [uxn][uxn] VM +* The `puff()` algorithm from [zlib][zlib] + What's next? See the [roadmap][roadmap]! -Development happens on [sourcehut][3]. +Development happens on [sourcehut][shproj]. Unlike Collapse OS which is a personal effort and doesn't lend itself well to collaboration, Dusk OS' wider scope makes it fitting for a collective effort. -Let's discuss this on its [public mailing list][4]. +Let's discuss this on its [public mailing list][mailinglist]. ## Build and run Dusk @@ -218,9 +221,9 @@ BIOS" mode. [usage]: fs/doc/usage.txt [dict]: fs/doc/dict.txt [roadmap]: ROADMAP.md -[3]: https://sr.ht/~vdupras/duskos -[4]: https://sr.ht/~vdupras/duskos/lists -[5]: fs/tests/comp/c/test.c +[shproj]: https://sr.ht/~vdupras/duskos +[mailinglist]: https://sr.ht/~vdupras/duskos/lists [duskcc]: fs/doc/cc/index.txt [fiwix]: https://www.fiwix.org [uxn]: https://wiki.xxiivv.com/site/uxn.html +[zlib]: https://github.com/madler/zlib diff --git a/fs/doc/design/simple.txt b/fs/doc/design/simple.txt @@ -14,7 +14,7 @@ reference when comparing complexity is Fabrice Bellard's Tiny C Compiler. Tcc enjoys a very good reputation among geeks, and Fabrice Bellard is generally considered to be a genius. Nevertheless, Dusk's C compiler, excluding backends, -is 1600 lines of code and tcc, excluding backend is roughly 30,000 lines of +is 1200 lines of code and tcc, excluding backend is roughly 30,000 lines of code. At the time of this writing, Dusk CC isn't quite completed yet, but there isn't much left to add, I don't think it will exceed 2000 lines by much.