| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Used Plan9's libc as starting point. This cleans up dangling references
due to loss of libc.
|
|
Commented out libc includes to uncover all explicit dependencies.
A large fraction has now been ported over (no testing).
I did not port over the command line tools, such as the rc shell.
These will be done independently - as of now I just want the library to
stand independent.
Compilation currently fails due to the lack of math functions.
|
|
We use weak linking to ensure we clean up at exit time correctly. If
libc is linked, then we call our cleanup function by registering an
atexit callback with the library. If libc is not linked, we have a weak
symbol that results in a noop. Similarly, if we call rt·exit while
linked with libc, this immediately calls libc's exit (which will call
our cleanup as we registered it). If we are not linked to libc, exit()
is given as a weak link to a noop function.
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
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...
|
