> That will make it part of the kernel ABI, since the mapping depends on > the running kernel, doesn't it?
Well, not the permanent ABI in the sense that AT_* et al are. This mapping must agree among all users sharing the same ld.so.cache file. That is all. So if you were to change the meaning of a bit that was used before with a different string, then you could not have the conflicting ld.so.conf.d files both installed at the same time (ldconfig will complain and fail). If you wanted to have two kernels both installed that disagree on the string for a given bit, then you'd have to switch the ld.so.conf.d files and re-run ldconfig when you switch which kernel you're booting. There are 32 bits free now. One can anticipate that reassigning a bit would come up only after these are exhausted. With prudent use, this will take a very long time to happen. Then the oldest CPU type string might be retired to reuse its bit. It seems unlikely that there will be a single installation (root directory) that really needs to have installed both a kernel optimized for the oldest CPU model known and a kernel optimized for the newest CPU model known. If there is, we can worry about it then. At any rate, the point remains that these bit assignments are not part of any published userland ABI one has to think about in all the ways that the real ABI implies. There is nowhere that has to know them or will ever consider them, except the kernel with the vDSO image built inside and the ld.so.conf.d file that goes with it. Thanks, Roland _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
