From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: [PATCH 2/2] gnu: icecat: Use libjpeg-turbo instead of bundled libjpeg. Date: Sun, 27 Nov 2016 23:28:45 +0100 Message-ID: <87twastv4y.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> References: <20161127201707.3789-1-me@tobias.gr> <20161127201707.3789-2-me@tobias.gr> <20161127205618.GC27187@jasmine> <20161127214119.GB30774@jasmine> <87wpfotwwk.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54220) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cB7wJ-000354-Ne for guix-devel@gnu.org; Sun, 27 Nov 2016 17:28:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cB7wG-0006k0-JP for guix-devel@gnu.org; Sun, 27 Nov 2016 17:28:51 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:51836) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cB7wG-0006iu-FL for guix-devel@gnu.org; Sun, 27 Nov 2016 17:28:48 -0500 In-Reply-To: <87wpfotwwk.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Leo Famulari , Tobias Geerinckx-Rice Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Marius Bakke writes: > Leo Famulari writes: > >> On Sun, Nov 27, 2016 at 10:02:35PM +0100, Tobias Geerinckx-Rice wrote: >>> Leo, >>>=20 >>> On 27/11/16 21:56, Leo Famulari wrote: >>> > Will this work on nachines that don't support SSE? My understanding is >>> > that we don't wish to require it. >>>=20 >>> Why wouldn't it? >>>=20 >>> I don't often use Icecat, but when I do... I don't see why it would >>> require SSE by default. ;-) And it's not like we ever patched it to use >>> IJG's libjpeg to begin with. >> >> I'm not sure, but the comment seems to indicate that we don't want to >> use it: >> >> ;; According to >> ;; http://sourceforge.net/projects/libjpeg-turbo/ , >> ;; "libjpeg-turbo is a derivative of libjpeg that >> ;; uses MMX, SSE, SSE2, and NEON SIMD instructions >> ;; to accelerate baseline JPEG compression/ >> ;; decompression", so we had better not use it > > SSE is pentium III, and SSE2 was introduced in Pentium IV. MMX is even > older. Are we really committed to supporting 15+ year old hardware? Digging a bit further, SSE2 is actually part of the AMD64 specification[0]. Perhaps we could make it conditional on architecture? 0: https://en.wikipedia.org/wiki/SSE2#CPU_support --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlg7Xh4ACgkQoqBt8qM6 VPpoCwgAs2mN1xslBcx+6IC3HjAfNVbq8F0kN9Qp/PdXJX5Wi20ppk0KoUWH60CV EkloNRJtrWX8rCMyZcgjcE8KzVZve1Hxl+B9l3YAi8DtZIraUcnMlV624azXKCa/ 5u4JStDa3a2XQpxVOzU7pQ7Jm7dc3maTGMw+12OJUcSM0kCDtHDFpifki+KysGUc cjEFc820kQTYlz+McXN6JJ9DmQHkSoYvcDM0YxCiCN9K/B6syvumJyoyNXydy73d jw6Y2pFowuY/3mJbvziUjPdpJtd0NKobW41zOipeVQzIDqv37ax044+3ZRy3P1cM rhC/ltuD3hqJALqMMQLlyrODhtrEMQ== =0afU -----END PGP SIGNATURE----- --=-=-=--