This is the mail archive of the
mailing list for the glibc project.
Re: support for calling Linux syscalls directly
- From: chrubis at suse dot cz
- To: "H. Peter Anvin" <hpa at zytor dot com>
- Cc: Mike Frysinger <vapier at gentoo dot org>, libc-alpha at sourceware dot org,keescook at chromium dot org
- Date: Tue, 12 Feb 2013 18:46:38 +0100
- Subject: Re: support for calling Linux syscalls directly
- References: <firstname.lastname@example.org><5109A662.email@example.com>
> I have had a number of discussions with people on this topic,
> especially given that syscall(3) is fundamentally flawed on a number
> of architectures, and that some architectures have been forced to use
> nonstandard signatures, complicating things.
I do the LTP which makes legitimate use of syscall(3) as for the
testing purposes we need to be able to call bare syscalls in order to
validate both glibc and kernel API. And removing the call would mess
Having suitable replacements in glibc wouldn't help much as we would
need either to add #ifdefs into each test that uses it or carry a copy
of the syscall wrappers inside the LTP.