On Jun 12, 2012, at 1:26 PM, Konstantin Belousov wrote: > On Tue, Jun 12, 2012 at 05:56:12PM +0200, Jan Sieka wrote: >> Both versions work indeed. I have analysed other architectures' >> lib/libc/<arch>/Symbol.map files and __flt_rounds should go into FBSD_ and >> *not* into FBSDprivate section. I have verified that at least one of the >> Perl's libraries (POSIX.so) links to __flt_rounds. Python also links to >> this function. So to the best of my knowledge current patch is the >> righteous one. > > Let me restate my point again. It does not matter whether some application > uses the symbol. It does matter whether the symbol is considered the part > of exported stable ABI, intended for use by applications. If it is, then > FBSD_1.X is the right namespace, otherwise symbol should be moved to > private and existing usage fixed. That particular symbol is in FBSD_1.0 for amd64, i386, ia64, powerpc, powerpc64, sparc64. It's in FBSDPrivate_1.0 for arm. It's not defined for mips at all. The latter two seem to be bugs; I just committed r237039 to fix arm. I haven't checked the situation on mips. TimReceived on Thu Jun 14 2012 - 01:27:45 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:28 UTC