Re: setXid

[Ulrich Drepper <drepper at redhat dot com>]

-----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-----