From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>, Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: icecat: Use libjpeg-turbo instead of bundled libjpeg.
Date: Sun, 27 Nov 2016 22:50:35 +0100 [thread overview]
Message-ID: <87wpfotwwk.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20161127214119.GB30774@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
Leo Famulari <leo@famulari.name> writes:
> On Sun, Nov 27, 2016 at 10:02:35PM +0100, Tobias Geerinckx-Rice wrote:
>> Leo,
>>
>> 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.
>>
>> Why wouldn't it?
>>
>> 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?
The NEON SIMD instruction seems to be ARM-specific and is available at
least on Cortex A8, which is an ARMv7 design.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2016-11-27 21:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 20:17 [PATCH 1/2] gnu: Add libjpeg-turbo Tobias Geerinckx-Rice
2016-11-27 20:17 ` [PATCH 2/2] gnu: icecat: Use libjpeg-turbo instead of bundled libjpeg Tobias Geerinckx-Rice
2016-11-27 20:56 ` Leo Famulari
2016-11-27 21:02 ` Tobias Geerinckx-Rice
2016-11-27 21:41 ` Leo Famulari
2016-11-27 21:50 ` Marius Bakke [this message]
2016-11-27 22:28 ` Marius Bakke
2016-11-27 22:44 ` Leo Famulari
2016-11-27 22:43 ` Leo Famulari
2016-11-27 23:15 ` Tobias Geerinckx-Rice
2016-11-27 23:20 ` Tobias Geerinckx-Rice
2016-11-27 23:42 ` Leo Famulari
2016-11-27 23:27 ` Leo Famulari
2016-11-27 20:55 ` [PATCH 1/2] gnu: Add libjpeg-turbo Leo Famulari
2016-11-27 21:12 ` Tobias Geerinckx-Rice
2016-11-27 21:36 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpfotwwk.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).