From owner-freebsd-bugs@FreeBSD.ORG Mon Jan 28 13:30:31 2008 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1777E16A419; Mon, 28 Jan 2008 13:30:31 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.freebsd.org (Postfix) with ESMTP id BF03A13C46A; Mon, 28 Jan 2008 13:30:30 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.14.1/8.14.1) with ESMTP id m0SD8QbV005632 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Jan 2008 08:08:27 -0500 (EST) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by aldan.algebra.com (8.14.1/8.14.1/Submit) id m0SD8QfR005631; Mon, 28 Jan 2008 08:08:26 -0500 (EST) (envelope-from mi+kde@aldan.algebra.com) From: Mikhail Teterin To: David Schultz Date: Mon, 28 Jan 2008 08:08:25 -0500 User-Agent: KMail/1.9.7 References: <200707051510.l65FAAEp090370@freefall.freebsd.org> <200801201650.45547@Misha> <20080128062943.GA82037@VARK.MIT.EDU> In-Reply-To: <20080128062943.GA82037@VARK.MIT.EDU> X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Cc: freebsd-bugs@freebsd.org Subject: Re: bin/96393: [libz] [patch] assembler implementations for libz on i386 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2008 13:30:31 -0000 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