C For C's Sake

@mato I think that sounds like a reasonable solution. I'm not too fond of the idea of having to deal with BPF macro code here either. Some other semi-related points:...

@ricarkol making the accessible amount smaller works well for some cases (preventing the allocation of extra extents; preventing attempts to write past block device limits which will result in an...

In posix you distinguish between application-generated exits and signal (/kernel)-imposed exits, here is a stackoverflow post that goes over this with pedantic attention to error code semantics :) https://stackoverflow.com/questions/5149228/return-value-range-of-the-main-function In...

I seem to have this issue, it's really annoying. I can work around it by creating smaller files, but that is a bit hacky. Consider this stuff required to play...

@alinpopa This is something that needs to be changed in `stdint`, and the author may or may not consider it out of scope. If the author would like the library...

@andrenth I found the issue, which turned out to be a dependency on `libgcc` introduced by the use of 64-bit uint64_t operations (division + modulo) in `uint64_stubs.c`, `uint128_stubs.c` and also...

@rixed I changed it to `-1/0/1` so these can be used with functors that expect that for `compare` (like `Map.S`) in my patch, but I'd like to have a go-ahead...

@rixed ah wow, learn something every day!

@andrenth Conditional compilation would work, but it would mean we would have to produce an additional static archive. Usually the mirage packages that ship C code would produce `libstdint_stubs+mirage-xen.a` and...

- I would like to have an interface with two steps: First choosing the storage backend (at compile-time), and choosing the argument to the storage backend (ie the path to...