Date: Sat, 16 Nov 2002 13:24:39 -0800 From: Marcel Moolenaar <marcel@xcllnt.net> To: Daniel Eischen <eischen@vigrid.com> Cc: arch@FreeBSD.ORG Subject: Re: What to do with userland *context() functions Message-ID: <20021116212439.GA1298@dhcp01.pn.xcllnt.net> In-Reply-To: <3DD66393.40AFC73@vigrid.com> References: <3DD66393.40AFC73@vigrid.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 16, 2002 at 10:26:11AM -0500, Daniel Eischen wrote: > After adding *context() as system calls, we no longer > need the userland versions. But I would like to use > them in libc_r and they might be useful to someone else > writing their own userland threading library. As of > now, we need different variants of them for libpthread, > so they aren't expected to be used there. > > How do folks feel about keeping them in libc, but named > as _getctx, _setctx, _swapctx? They would be similar > to _setjmp/_longjmp which don't save/restore the signal > mask. It'll add a little bloat to libc and they are > only present for i386 and alpha archs. I'd like them to be removed from libc. I tend to agree with Doug that the duplication (3 as it stands) is unattractive. Since libc_r has a short life expectancy, I would probably not bother to move them to libc_r. IMO, YMMV. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021116212439.GA1298>