Date: Mon, 28 Jan 2008 08:08:25 -0500 From: Mikhail Teterin <mi+kde@aldan.algebra.com> To: David Schultz <das@freebsd.org> Cc: freebsd-bugs@freebsd.org Subject: Re: bin/96393: [libz] [patch] assembler implementations for libz on i386 Message-ID: <200801280808.26164@aldan> In-Reply-To: <20080128062943.GA82037@VARK.MIT.EDU> References: <200707051510.l65FAAEp090370@freefall.freebsd.org> <200801201650.45547@Misha> <20080128062943.GA82037@VARK.MIT.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
On =D0=CF=CE=C5=C4=A6=CC=CF=CB 28 =D3=A6=DE=C5=CE=D8 2008, David Schultz wr= ote: =3D Our msun is based on Sun fdlibm, which is incomplete, and has not =3D been maintained by the vendor in over 15 years. In contrast, we do =3D a new libz import every few years. Alright, I offer OpenSSL as a better example. Different assembly pieces for= =20 different CPUs.. =3D I'd take it up with someone like des@, who did the last import, since he =3D will have to deal with any conflicts and other surprises on the next im= port. There are no conflicts -- that's the good part. No files "on the vendor's=20 branch" need modifications, because the vendor allows and supports=20 platform-specific assembly implementations of the hot functions... But, Ok, I'll try to approach someone else... Thanks, -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200801280808.26164>