From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] jpeg-turbo: add simd support for powerpc cores with altivec
Date: Sun, 11 Dec 2016 16:52:18 +0100 [thread overview]
Message-ID: <20161211155219.22814-3-peter@korsgaard.com> (raw)
In-Reply-To: <20161211155219.22814-1-peter@korsgaard.com>
From the 1.5-b1 release notes:
Added full SIMD acceleration for PowerPC platforms using AltiVec VMX
(128-bit SIMD) instructions. Although the performance of libjpeg-turbo on
PowerPC was already good, due to the increased number of registers available
to the compiler vs. x86, it was still possible to speed up compression by
about 3-4x and decompression by about 2-2.5x (relative to libjpeg v6b)
through the use of AltiVec instructions.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
package/jpeg/Config.in | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/package/jpeg/Config.in b/package/jpeg/Config.in
index 170e58c..926f12e 100644
--- a/package/jpeg/Config.in
+++ b/package/jpeg/Config.in
@@ -6,7 +6,8 @@ config BR2_PACKAGE_JPEG
# jpeg-turbo has simd support for some architectures
config BR2_PACKAGE_JPEG_SIMD_SUPPORT
bool
- default y if BR2_X86_CPU_HAS_MMX || BR2_ARM_CPU_HAS_NEON
+ default y if BR2_X86_CPU_HAS_MMX || BR2_ARM_CPU_HAS_NEON || \
+ BR2_POWERPC_CPU_HAS_ALTIVEC
if BR2_PACKAGE_JPEG
--
2.10.2
next prev parent reply other threads:[~2016-12-11 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 15:52 [Buildroot] [PATCH 1/4] jpeg-turbo: now checks for pkg-config Peter Korsgaard
2016-12-11 15:52 ` [Buildroot] [PATCH 2/4] jpeg: rework jpeg-turbo simd support handling Peter Korsgaard
2016-12-11 15:52 ` Peter Korsgaard [this message]
2016-12-11 15:52 ` [Buildroot] [PATCH 4/4] jpeg-turbo: add simd support for aarch64 Peter Korsgaard
2016-12-11 17:34 ` [Buildroot] [PATCH 1/4] jpeg-turbo: now checks for pkg-config Thomas Petazzoni
2016-12-11 17:37 ` Peter Korsgaard
2016-12-11 17:40 ` Thomas Petazzoni
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161211155219.22814-3-peter@korsgaard.com \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.