List view
Port nightingale to multiple architectures and maintain these ports to ensure I don't fall into any traps that will make supporting different CPUs more difficult in the future.
No due date•3/3 issues closedThe kernel and userland should use either the same code for the vast majority of libc. An example of why this is necessary can be seen in the similarity between `libc/stdio.c` and `kernel/print.c`, which share the same exact implementation of printf. This also allows future efforts like a sane memory allocator to be used and taken advantage of throughout the entire system. A great model for how this can be done is the sortix operating system, which uses the same libc codebase to build a `libk` object that is statically linked into the kernel and the userland library.
No due date•1/1 issues closed