Date: Mon, 2 Jul 2012 10:41:38 -0400 From: John Baldwin <jhb@freebsd.org> To: Richard Yao <ryao@gentoo.org> Cc: "hackers@FreeBSD.org" <hackers@freebsd.org> Subject: Re: How does bootinfo64.c find read_eflags() and write_eflags() on amd64? Message-ID: <201207021041.38640.jhb@freebsd.org> In-Reply-To: <4FF16CA4.2040700@gentoo.org> References: <4FF16CA4.2040700@gentoo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, July 02, 2012 5:40:52 am Richard Yao wrote: > /usr/src/sys/boot/i386/libi386/bootinfo64.c uses read_eflags() and > write_eflags(), which live as inline functions in > /usr/src/sys/i386/include/cpufunc.h. > /usr/src/sys/boot/i386/libi386/bootinfo64.c also includes > /usr/include/machine/cpufunc.h, but that is > /usr/src/sys/amd64/include/cpufunc.h on amd64, which does not contain > either of them. The boot utilities on amd64 are built as 32-bit binaries using -m32 and with 'machine' pointing to 'i386' instead of amd64. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201207021041.38640.jhb>