News for hackers. Stuff that matters.

A comment on Windows X86-64 System Call Table. Parent comment

Re:Windows X86-64 System Call Table by masklinn on Monday September 02, 2019 @03:02AM (#20857271)
> By not calling syscalls based on their numbers on Windows. That might sound crazy

Not really. Only on Linux are direct syscalls an official ABI. On most unices (e.g. solaris, BSDs, OSX) you must dynamically link and go through the platform's libc.

[ Parent | on HN ]
Re:Windows X86-64 System Call Table by earenndil on Monday September 02, 2019 @04:50AM (#20857691)
I don't know about solaris, and I know macos had kernel changes which broke go, but freebsd has a stable kernel interface and unstable userspace. (So does linux, for that matter--ever try running a program linked to a newer version of glibc?)
[ Parent | on HN ]
Re:Windows X86-64 System Call Table by account42 on Monday September 02, 2019 @07:23AM (#20858390)
> So does linux, for that matter--ever try running a program linked to a newer version of glibc?

That doesn't mean the interface isn't stable or at least not less stable than the kernel interface or literally any iterface for something that is still being developed.

It would be nice if glibc would provide an easy way to target the ABI of an older version (which is compatible with all newer versions) but you can do that the manual way by compiling and linking against that old version.

[ Parent | on HN ]