Age | Commit message (Collapse) | Author | |
---|---|---|---|
2021-11-20 | Chore: reorganize libutf and libfmt into base | Nicholas | |
I found the split to be arbitrary. Better to include the functionality in the standard library. I also split the headers to allow for more granular inclusion (but the library is still monolithic). The only ugliness is the circular dependency introduced with libutf's generated functions. We put explicit prereqs with the necessary object files instead. | |||
2021-11-20 | Feature: self hosting prototype implemented | Nicholas Noll | |
This is a large change. In order to remove myself from libc's arcane interface, I implemented an independent runtime layer. It is based on musl's wonderful implementation mostly. Critically, if libc is linked to the program, then we cooperate. Namely, we call start main and let libc do all initialization. If not, then we have a noop defined in rt3.a. The general structure of the file is: 1. sys/$os/$arch contains all architecture dependent code 2. sys/$os/port contains all code that depends on the os, but is portable 3. rt/$arch contains all the runtime architecture dependent code 4. rt/* contains the portable runtime code. Obviously testing is needed. Specifically, while code is checked in for the most popular architectures, it only has been tested on one computer! Overall this is exciting and as been educational. | |||
2021-11-19 | chore: make dependence on static syscalls explicit | Nicholas Noll | |
2021-11-18 | feat: continued filling out system layer | Nicholas Noll | |
2021-11-18 | feat: filling out system layer's interface | Nicholas Noll | |
2021-11-18 | filling out system layer | Nicholas Noll | |
2021-11-17 | automated platform specific code parsing | Nicholas Noll | |
2021-11-17 | update: sys | Nicholas | |
2021-11-17 | fix: mkfile names | Nicholas | |
2021-11-15 | Feat: prototype of self-hosted library | Nicholas | |
This is very much a work in progress. Still ruminating on the structure of the library. It feels right but I want a more "social" presence - namely the ability to link to a libc seemlessly. The solution is most likely weak aliasing that musl uses - but musl itself weak aliases global symbols, e.g malloc. We would have to define weak internal symbols that musl defines as strong links but this knows too much about the internals of musl... |