SYS_calls should be bound

[nagisa]

Since there’s a binding to syscall function, SYS_* constants should also be bound. Perhaps in their own module, since there’s so many of them.

• Linux (???)
• Android where _NR are defined in unistd{32,64};
• FreeBSD;
• NetBSD;
• OpenBSD;
• Apple

[alexcrichton]

Sounds good to me, should be relatively easy enough to add at any time!

[kamalmarhubi]

I am willing to take this on. I've been wanting to script getting constants anyway—at least on Linux— and this is a great excuse.

[kamalmarhubi]

Also re Linux, I found the easiest place to get the sycall numbers is actually in from musl source, eg:

• http://git.musl-libc.org/cgit/musl/tree/arch/aarch64/bits/syscall.h
• http://git.musl-libc.org/cgit/musl/tree/arch/powerpc/bits/syscall.h

It'll be worth putting these in a joint musl / other location though. Probably unix::notbsd::linux::syscalls, which will be included by both unix::notbsd::linux with target_arch guards.

[alexcrichton]

For now I'd prefer to just stick with duplication, it's not that hard to have and it presents a much more understandable organization hierarchy

[kamalmarhubi]

Sounds good.

[posborne]

👍 for scripting this and getting consistent, complete coverage.

[Susurrus]

@alexcrichton I think this is addressed as there are tons of SYS_* constants now in libc.

[alexcrichton]

Indeed!