| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2023-02-25 | toolchain: working customized toolchain for userland bins | dzwdz | |
| 2023-02-24 | toolchain: partially set up the sysroot | dzwdz | |
| 2023-02-23 | toolchain: update, move to a Camellia-specific toolchain | dzwdz | |
| 2022-07-27 | tools/stacktrace_resolve.awk: fix the kernel binary path | dzwdz | |
| 2022-07-26 | tools: add tools/sort_includes.rb | dzwdz | |
| 2022-07-16 | amd64: barely boot into kernel code | dzwdz | |
| 2022-07-11 | user: reorganize the userland sources | dzwdz | |
| 2022-07-09 | syscalls/pipe: turn into a POSIX-style api with separate rw ends | dzwdz | |
| Without separate read/write ends you can't tell when there are no more writers left if you have multiple readers. Consider this piece of code: int fd = pipe(); fork(); // execution continues in 2 processes while (read(fd, &some_buf, sizeof somebuf) >= 0) { ... } Once both processes call `read()`, it's obvious that no writes are possible - all the processes that hold a reference to the pipe are currently stuck on a `read()` call, so the kernel could just make it return an error in both. But, what then? It's still possible to write to the pipe, and you can't know if the other process will do that. Thus, if you don't want to miss any output, you have to keep reading the pipe. Forever. Both processes end up stuck. Having separate read/write ends prevents that. | |||
| 2022-06-30 | syscall_wrappers: generate casts so the compiler doesn't complain | dzwdz | |
| 2022-05-03 | kernel/alloc: print who allocated unfreed memory on shutdown | dzwdz | |
| 2022-05-03 | kernel: stacktraces on panic() | dzwdz | |
| 2022-05-02 | meta: write a script to generate `src/init/syscalls.c` | dzwdz | |
| 2021-08-07 | build all parts of the toolchain to the same $PREFIX | dzwdz | |
| If gcc is built with a different $PREFIX than binutils, it won't even attempt using them - it will use the system assembler instead, which fails for obvious reasons. | |||
| 2021-08-06 | a (seemingly broken) gcc build script | dzwdz | |
| It compiles, but the resulting gcc binary doesn't actually work. Maybe it's too new for the binutils? | |||
| 2021-08-06 | quit the binutils build script if an error occurs | dzwdz | |
| 2021-08-05 | add a script which builds i686-elf-binutils | dzwdz | |
| 2021-07-10 | implement a basic linter | dzwdz | |
| Currently it just checks if the kernel doesn't accidentally use arch-dependent headers. | |||
 |
index : camellia | |
| Unnamed repository; edit this file 'description' to name the repository. |
| summaryrefslogtreecommitdiff |