From owner-freebsd-current Mon Sep 6 11:44: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 76FDA14D2E; Mon, 6 Sep 1999 11:43:52 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id OAA03894; Mon, 6 Sep 1999 14:41:58 -0400 (EDT) (envelope-from wollman) Date: Mon, 6 Sep 1999 14:41:58 -0400 (EDT) From: Garrett Wollman Message-Id: <199909061841.OAA03894@khavrinen.lcs.mit.edu> To: Marcel Moolenaar Cc: current@FreeBSD.ORG, jb@FreeBSD.ORG Subject: Signal changes and {,sig}{set,long}jmp In-Reply-To: <37D3FB0E.94662026@scc.nl> References: <37D38367.C297FD64@scc.nl> <199909061607.MAA03384@khavrinen.lcs.mit.edu> <37D3FB0E.94662026@scc.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > The setjump/longjump family of functions are userland function > AFAICT. POSIX doesn't make any such distinction. Remember that setjmp/longjmp *already* enter the kernel, in order to save/restore the signal mask, so there isn't any real performance penalty! (Programs which need a cheaper version already have to use _{set,long}jmp, which doesn't play with the signal mask.) > this issue is basicly independent of the sigset_t change. Not entirely. If we are going to be making substantial changes in the internals of the Standard Library, then it makes more sense to put all of the changes together. If we're already changing sizeof(jmp_buf) and sizeof(struct sigcontext), then at a minimum it makes sense to have them be the same shape (which as I mentioned could simplify the thread scheduler). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message