Date: Fri, 14 Dec 2007 01:22:32 -0500 From: David Schultz <das@FreeBSD.ORG> To: Alexander Kabaev <kabaev@gmail.com> Cc: Daniel Eischen <deischen@FreeBSD.ORG>, Yar Tikhiy <yar@FreeBSD.ORG>, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/lib/msun Symbol.map Message-ID: <20071214062232.GA32835@VARK.MIT.EDU> In-Reply-To: <20071213235617.2b554b60@kan.dnsalias.net> References: <200712140308.lBE38Ae7061160@repoman.freebsd.org> <20071213235617.2b554b60@kan.dnsalias.net>
index | next in thread | previous in thread | raw e-mail
On Thu, Dec 13, 2007, Alexander Kabaev wrote: > > http://cvsweb.FreeBSD.org/src/lib/msun/Symbol.map.diff?r1=1.5&r2=1.6 > > This is just wrong IMHO. New exported symbols should not be introduced > carelessly and certainly not should be added to the same namespace that > exists in 7.0. Either we add these to 7.0 before it releases, or they > should go into their own section which will start collecting all new > libc symbols to appear in 8.0. > > Daniel, Yar - what is your take on this? Well, I don't particularly care, but I'll explain why I didn't think it was important. The symbols I added are reserved for use in the C math library according to C99. Hence, any valid C program compiled against libm.so.5 will not be affected. Furthermore, I've been adding C99 functions to libc/libm little by little for years. Occasionally people request that I MFC some of them, and I do. Some of them get MFC'd before X.1-RELEASE, some of them get MFC'd before X.2-RELEASE, and so on. Of course, if these symbols get new versions when they get MFC'd to -STABLE, they need to be versioned in -CURRENT as well. In other words, the payoff for being pedantic is low, and the cost is moderately high. So while I don't feel strongly about this, it seems easier to declare that programs that abuse reserved C99 symbols are not guaranteed to work, neither now nor in the future.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071214062232.GA32835>