From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21257 invoked by alias); 20 Sep 2004 20:19:07 -0000 Mailing-List: contact libc-hacker-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-hacker-owner@sources.redhat.com Received: (qmail 21241 invoked from network); 20 Sep 2004 20:19:07 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 20 Sep 2004 20:19:07 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.10) with ESMTP id i8KKJ77q029790 for ; Mon, 20 Sep 2004 16:19:07 -0400 Received: from lacrosse.corp.redhat.com (lacrosse.corp.redhat.com [172.16.52.154]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i8KKJ7r27440; Mon, 20 Sep 2004 16:19:07 -0400 Received: from [10.0.1.84] (drepper.cipe.redhat.com [10.0.1.84]) by lacrosse.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i8KKJ0a07187; Mon, 20 Sep 2004 16:19:01 -0400 Message-ID: <414F3B29.1040701@redhat.com> Date: Mon, 20 Sep 2004 20:19:00 -0000 From: Ulrich Drepper Organization: Red Hat, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a4) Gecko/20040915 MIME-Version: 1.0 To: Roland McGrath CC: GNU libc hacker Subject: Re: setXid References: <200409201950.i8KJoIJb015512@magilla.sf.frob.com> In-Reply-To: <200409201950.i8KJoIJb015512@magilla.sf.frob.com> X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SW-Source: 2004-09/txt/msg00077.txt.bz2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Roland McGrath wrote: > Like I said, they haven't been presented with an implementation yet. I actually did. I had all accesses to the values wrapped in macros, then add a pointer, and have them, on demand, point to one single variable in the thread group struct. > What > I would propose would allow such an extension and also implement correct > semantics when you are not using it. You'll probably come up with the same method. Have fun! > You did not respond at all to my objection to your glibc extension > functions. Please say something about how you intend these to be > acceptable features. I don't understand the problem. This extensions just provide a way to access the behavior which has been in use forever. Whenever I brought the setXid topic up some people said "why multi-threaded program needs the existing behavior". These extensions are honestly as well defined (or better) than the POSIX mandated behavior and they are necessary for people who actually want the behavior (at least for migration purposes). I see no problem at all. If another OS does not provide the functionality the functions can fail. - -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFBTzsp2ijCOnn/RHQRAt3GAJ9ToOogBS9phmUqF2htpYFNq60PrQCfZd62 mv70VcGJt4DO3O8yZZM+c/E= =z0EN -----END PGP SIGNATURE-----