From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 42906198005 for ; Tue, 26 Feb 2013 13:46:46 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 88E13E0790; Tue, 26 Feb 2013 13:46:44 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 90E40E0776 for ; Tue, 26 Feb 2013 13:46:43 +0000 (UTC) Received: from [192.168.1.2] (pool-173-77-245-118.nycmny.fios.verizon.net [173.77.245.118]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ryao) by smtp.gentoo.org (Postfix) with ESMTPSA id 60DB333DBF3 for ; Tue, 26 Feb 2013 13:46:42 +0000 (UTC) Message-ID: <512CBCAA.4070508@gentoo.org> Date: Tue, 26 Feb 2013 08:46:18 -0500 From: Richard Yao User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121128 Thunderbird/10.0.11 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Evaluating a new malloc() References: <512CB9B8.9060308@gentoo.org> <512CBA2F.7090806@flameeyes.eu> In-Reply-To: <512CBA2F.7090806@flameeyes.eu> X-Enigmail-Version: 1.3.5 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1A51B645D1FFF3B4937B56AB" X-Archives-Salt: 107aefb2-3ffa-4ad2-8962-e431537bc398 X-Archives-Hash: 03814c6297e11ebec9a108a55625ff3c This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1A51B645D1FFF3B4937B56AB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 02/26/2013 08:35 AM, Diego Elio Petten=C3=B2 wrote: > On 26/02/2013 14:33, Richard Yao wrote: >> Results such as these led Blender and others (e.g. Chrome/Chromium, >> Firefox, Thunderbird) to bundle private versions of jemalloc. This >> bundling situation violates our policy against bundled libraries. The >> maintainers could just patch their software to link to libjemalloc. >> However, it might make more sense to evaluate jemalloc as a >> distribution-wide replacement for glibc's ptmalloc. >=20 > Short answer: no. >=20 Would you elaborate on this? From a brief chat in IRC, you mentioned Valgrind, but it looks like that issue has been solved: http://blog.mozilla.org/jseward/2012/06/05/valgrind-now-supports-jemalloc= -builds-directly/ jemalloc probably should be merged at glibc upstream, but I have zero contact with glibc development, my Google searches have been fruitless and I want to know what other people think about this. I think it would be wrong to try to go to upstream with the idea if people downstream don't like the idea. Not to mention, glibc is not the only libc in Gentoo and this applies to each of them. --------------enig1A51B645D1FFF3B4937B56AB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJRLLyuAAoJECDuEZm+6ExkkqIP/RM9DsnilQ3xp/IIgWCtPO7x j4Yx6JJI/Y8ZrHt016zJB8OWKPGdUcPEC0oAH75ZgVGecAhQYpS5oQby1EHJsx42 /lxEFOQOXFlWGijuho3YRwxXwjh0LLXe3f4SU4H/mo+mH7VvUx/6+iHgw+9hRCCR tb3928X9J2yxDVTy8rrhIV95iQmcU7ggIl6nqRnoJ7eZ/pdYjMFWzPYmrLWQxs1f Dtu+TFBU2vrgPl8wVVt1s4QbfyOtGjfm9INJvvlGnUmfIw7sVKmbfTNenCUa1OUK OKG3AXe6m9OyUcDtbuJP2uIPGEi2qR8w0r8T2mQ4ixyJxjcpAR9K4mLxSVh9ACig /ptrMG6F1dyWShHbLSFi9Smr0rbHQIjgt/C+5VUxjbc/iY8eSlJ0AEtEE6RbrZFV 245BYG2TgA09/fUfsUH02BuThuT2jC3zAENYS4tnVb2tnT8fhox7IWmCeysROoCI 3JngqKbj1ULARYqt2t1ff1jrlRbD2RhCGpnBXfyIMHqugAG4cx4hrCuePPzXOplW n4aL7Vyk4DyVHvLCWLtgy8Sh2MGcuvHKrHGQi3NYLD54sSNbDajkQ3V0s1fnyXj2 OeryRRb2+HRfiTkhzalCJlggyl0PYMiKX48xXBji9aAYu0uvpTDsZ4vty2kOV0N2 Bpkw2BFS3VgB5KqHlnzq =0vDu -----END PGP SIGNATURE----- --------------enig1A51B645D1FFF3B4937B56AB--