Porting Rust's Std to Rustix

Re:Porting Rust's Std to Rustix by ylyn on Tuesday January 04, 2022 @08:27AM (#29794438)

> This is a bit different from Linux, where the abstractions are layered the other way round: the OS (POSIX) spec mostly assumes an existing libc.

FWIW the POSIX spec assumes libc, but on Linux specifically the syscall interface is stable.

[ Parent | on HN ]

Re:Porting Rust's Std to Rustix by sanxiyn on Tuesday January 04, 2022 @08:30AM (#29794463)

Note that macOS syscall interface is specifically unstable so Rust needs POSIX/libc path anyway.

[ Parent | on HN ]

Re:Porting Rust's Std to Rustix by masklinn on Tuesday January 04, 2022 @09:23AM (#29795016)

Also on Solaris/Illumos/SmartOS/..., and on OpenBSD (where it's more or less verboten entirely since system-call-origin verification).

[ Parent | on HN ]

Re:Porting Rust's Std to Rustix by wahern on Tuesday January 04, 2022 @07:06PM (#29802888)

AFAIU, you don't need to use libc on OpenBSD, however only one contiguous region of code is permitted to invoke syscalls, and so you can't mix-and-match ad hoc libraries. See https://man.openbsd.org/msyscall, which implements one-time registration of a contiguous range of pages permitted to invoke syscalls.

[ Parent | on HN ]

Re:Porting Rust's Std to Rustix by codeflo on Tuesday January 04, 2022 @08:56AM (#29794737)

Thanks, that’s a great correction/clarification.

[ Parent | on HN ]