Date: Sat, 25 Jun 2016 10:02:38 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Brooks Davis <brooks@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: HEADS UP: caution required with updates using custom kernels Message-ID: <20160625070238.GG38613@kib.kiev.ua> In-Reply-To: <20160624225034.GC20770@spindle.one-eyed-alien.net> References: <20160623210751.GB7860@spindle.one-eyed-alien.net> <20160624060019.5e650ad9.ohartman@zedat.fu-berlin.de> <20160624155111.GB20770@spindle.one-eyed-alien.net> <330789230754140e38fb527973e23405@ultimatedns.net> <20160624225034.GC20770@spindle.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 24, 2016 at 10:50:34PM +0000, Brooks Davis wrote: > pipe(2) had an unnecessarily odd calling convention (ignoring the > argument the user thought they were passing and returning the two file > descriptors via the two return registers). This required machine > dependent assembly for every target and special handling in tracing > tools (ktrace, dtrace, etc). On 64-bit platforms, pipe(2)'s > implementation is the only reason the two-register return model needs to > exist at all (on 32-bit platforms it allows off_t to be returned from > lseek). getpid() is another instance.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160625070238.GG38613>