Date: Mon, 18 Oct 2010 14:11:31 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Eugene Grosbein <eugen@grosbein.pp.ru> Cc: hackers@freebsd.org Subject: Re: syscall Message-ID: <20101018111131.GE2392@deviant.kiev.zoral.com.ua> In-Reply-To: <4CBC2109.4030303@grosbein.pp.ru> References: <4CBC2109.4030303@grosbein.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Mon, Oct 18, 2010 at 05:27:21PM +0700, Eugene Grosbein wrote: > Hi! > > I've written an utility in C that does not link libc normally, > instead it includes <sys/syscall.h> and calls syscall(). > It works nice for FreeBSD8/i386. > > Now I'm porting it to FreeBSD8/amd64 and just cannot find > how to call syscall() directly from C code. Show what you tried to do. Syscall() at the C-level works the same (well, almost, but the differences are too subtle for this discussion) for all architectures. > > For arm, i386 and mips there are: > > lib/libc/arm/sys/syscall.S > lib/libc/i386/sys/syscall.S > lib/libc/mips/sys/syscall.S amd64 syscall() wrapper code is autogenerated. > > What about amd64? Indeed, what is your issue with amd64 ? > > Eugene Grosbein > > P.S. Please reply to the list. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAky8K2MACgkQC3+MBN1Mb4golQCgnlIWsqHLxukhcm5sD/9OPdmz 7iQAoIC1L5q0Rzd14/eRDRLukbzoXG9q =yGkH -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101018111131.GE2392>