News for hackers. Stuff that matters.
Re:A turning point for GNU libc by derleth on Tuesday April 03, 2012 @12:55PM (#3793734)
> use syscalls directly(well, except on Windows, for obvious reasons)

Not obvious to me. Please elucidate.

Re:A turning point for GNU libc by wtracy on Tuesday April 03, 2012 @01:13PM (#3793823)
Microsoft doesn't make the specs for the interface between the Windows kernel and the win32 libraries public.
Re:A turning point for GNU libc by yuhong on Tuesday April 03, 2012 @03:23PM (#3794373)
Nor it is been stable. Win8 for example changes this interface.
Re:A turning point for GNU libc by koenigdavidmj on Tuesday April 03, 2012 @01:11PM (#3793812)
Even the Windows API `system calls', like CreateProcess, are just wrappers around NT system calls. There are other wrappers too, like the Subsystem for UNIX Applications (which implements a POSIX API on top of the same NT calls).
Re:A turning point for GNU libc by xpaulbettsx on Tuesday April 03, 2012 @07:33PM (#3795354)
You cannot call syscalls directly, as the syscall table is generated dynamically from the kernel source code on NT. The closest thing you can do is call the Nt* class of functions, which are often direct thunks to syscalls.