This is the mail archive of the libc-hacker@sourceware.org mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
From: Jakub Jelinek <jakub@redhat.com> Date: Tue, 3 Jan 2006 22:36:11 +0100 > The following patch (almost) implements what has been outlined in > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161736 > The major changes from that outline are that it should (am still verifying > that) cause no changes whatsoever for sparcv9 or sparc64 built glibc, > sparc built glibc's shared libraries expected to work properly just on > pre-v9 CPUs and sparc built .a libraries (and therefore statically linked > 32-bit binaries too) be able to cope with both, by using CAS on 64-bit > CPUs and various hacks on 32-bit CPUs. > > So far I have done sparc-linux NPTL build and make check (worked fine), > am sparcv9-linux NPTL build and make check, plus verified that stripped > libc.so/libpthread.so are identical on sparcv9-linux without and with this > patch. > > As written in the outline, on pre-v9 CPUs it uses the ldstub lock pool > indexed by hashed address for most of the atomic stuff, ldstub lock > in the upper 8 bits of the 32-bit value for locks (where only 0, 1 and 2 > are valid values (but anything < 16M is ok) and for process shared > barriers as well as all semaphores uses a ldstub lock in the padding > between the (smaller) internal structure and bigger exported type. Thanks for getting around to this work Jakub. At a minimum I'll do build/test runs on sparc{,v9,v9b,64,64b}-linux.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |