From owner-freebsd-arch Sat Nov 16 13:25:26 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D08737B401 for ; Sat, 16 Nov 2002 13:25:25 -0800 (PST) Received: from kayak.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51A7543E3B for ; Sat, 16 Nov 2002 13:25:10 -0800 (PST) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by kayak.xcllnt.net (8.12.6/8.12.6) with ESMTP id gAGLOq0N039853; Sat, 16 Nov 2002 13:24:55 -0800 (PST) (envelope-from marcel@kayak.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.6/8.12.6) with ESMTP id gAGLOqUq001354; Sat, 16 Nov 2002 13:24:52 -0800 (PST) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.6/8.12.6/Submit) id gAGLOdf0001353; Sat, 16 Nov 2002 13:24:39 -0800 (PST) (envelope-from marcel) Date: Sat, 16 Nov 2002 13:24:39 -0800 From: Marcel Moolenaar To: Daniel Eischen Cc: arch@FreeBSD.ORG Subject: Re: What to do with userland *context() functions Message-ID: <20021116212439.GA1298@dhcp01.pn.xcllnt.net> References: <3DD66393.40AFC73@vigrid.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DD66393.40AFC73@vigrid.com> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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