On Aug 4, 2015, at 8:06 AM, Roland McGrath <roland@xxxxxxxxxxxxx> wrote: > I think we are asserting that they are exactly that by dint of the confstr > results for _CS_POSIX_V7_ILP32_OFF32_CFLAGS et al. So the question is what > POSIX actually does or doesn't say about process-shared synchronization > objects being shared between processes running programs built in different > POSIX compilation environments. > > The other relevant question is whether 32/64 sharing of each particular > pshared object has in fact worked reliably under glibc in the past. Since > we haven't been clear and explicit about the subject before AFAIK, then if > in fact it worked before then people might well have inferred that we made > such an ABI guarantee. (I hope not, since if so we just broke it.) The relevant questions aren't what's the least useful behavior that POSIX lets us get away with or can we leave it broken because it never worked;'the questions are what do the other operating systems do and what do the users want. IIRC, the first I ever heard of this issue was Keith Packard complaining that he couldn't put a mutex in shared memory because then 32-bit X clients couldn't talk to a 64-bit X server and it was too bad it didn't work on Linux because it does work on Solaris. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
