[saagarjha]

Using .ascii is fine; the string is going to a syscall–not libc. And using the standard library in a program like this is kind of beside the point…

[andy_threos_io]

nope, every decent OS has system call library you can write like:

  bl _Open ; whatever syscall name you have

and the linker or the OS dynamic linker will get you the proper system call code, with the numbers.

BTW even in our small threos.io os we use dynamic linked system calls.

[saagarjha]

I know how dynamic linkers work and am not arguing against using the libc interface in general. I'm saying that this program intentionally doesn't use those interfaces.

[vetinari]

This can be a problem on macOS; Apple doesn't keep compatibility among releases at sysenter level.

Golang used to run into this, they switched to using libSystem in 1.11: https://golang.org/doc/go1.11#runtime

[andy_threos_io]

The system call library is NOT libc.

[saagarjha]

Then Apple doesn't have it.

[andy_threos_io]

/usr/lib/system/libsystem_kernel.dylib

[andy_threos_io]

you don't know about it

/usr/lib/system/libsystem_kernel.dylib

ex. https://stackoverflow.com/questions/37656016/osx-setgid-syst...

[saagarjha]

That's part of libSystem, macOS's libc implementation…