libc

[Dave Wilkinson]

XOmB loads and executes James' test application compiled with his newlib port and gcc. It fails with a divide by zero in _exit(), but otherwise runs correctly. (exit isn't implemented... again). The test app runs atoi, and it returns 4, like expected.

Kinda lackluster, but also kinda awesome. XOmB has userspace as of today, Programmers' Day 2009.

[Brian Madden]

Sweet work!  Is this on deadreckoning or on ash?

Brian

[Steve Klabnik]

wow. congrats you two. Fucking bad-ass.

[Dave Wilkinson]

deadreckoning... still plodding through the x86. Will be neat to have a C standard library working.

On Sun, Sep 13, 2009 at 7:45 PM, Brian Madden <untw...@gmail.com> wrote:

[James Larkby-Lahet]

w0000t!

Wilkie, I'll write you an _exit(), and maybe even call it
automatically from crt0 (the C 'runtime') if you're good :)

Hopefully I can get Adam to help me write some maus scripts, and then
we can all has libc && x86_64-pc-xomb-gcc, hot off the git.

Right now, we have libc, meaning that all C programs that use only
standard includes can now be built to run on XOmB. However, if any of
the library calls you make issue a system call, an error code is
returned.

There are 17 system calls newlib uses, in 3 groups:
- process management (fork, exec, kill, getpid, etc)
- I/O (open, read, write, etc.)
- misc. (sbrk for memory, and times() for system time)

Writing the process and misc. syscalls should be straightforward. We
will need to write a simple RAM filesystem to support the I/O, and
then we will, for example, be able to run GCC (a pretty complicated
program if I may say) on XOmB!

my congratulations and thanks to all who have helped XOmB get to this point,

James

[Adam Hobaugh]

It won't be very hard to get the install scripts written, I tried to
make it as straight forward as possible. We can either work that out
next time I see you or over gchat.

//adam