DRC d38b4f21ec Optimize ARM64 SIMD code for Cavium ThunderX ...

Per @ssvb:
ThunderX is an ARM64 chip that dedicates most of its transistor real
estate to providing 48 cores, so each core is not as fast as a result.
Each core is dual-issue & in-order for scalar instructions and has only
a single-issue half-width NEON unit, so the peak throughput is one
128-bit instruction per 2 cycles.  So careful instruction scheduling is
important.  Furthermore, ThunderX has an extremely slow implementation
of ld2 and ld3, so this commit implements the equivalent of those
instructions using ld1.

Compression speedup relative to libjpeg-turbo 1.4.2:
48-core ThunderX (RunAbove ARM Cloud), Linux, 64-bit: 58-85% (avg. 74%)
relative to jpeg-6b: 1.75-2.14x (avg. 1.95x)

Refer to #49 and #51 for discussion.

Closes #51.

This commit also wordsmiths the ChangeLog entry (the ARMv8 SIMD
implementation is "complete" only for compression-- it still lacks some
decompression algorithms, as does the ARMv7 implementation.)

Based on:
9405b5fd03

which is based on:
f561944ff7
962c8ab21f

2016-01-16 02:39:02 -06:00

..

CMakeLists.txt

SSE2 SIMD implementation of Huffman encoding

2016-01-12 03:03:49 -06:00

jccolext-altivec.c

Extend the AltiVec VMX SIMD routines to support little endian PowerPC platforms.

2015-02-20 19:57:21 +00:00

jccolext-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jccolext-sse2-64.asm

Fix x86-64 ABI conformance issue in SIMD code

2015-09-16 22:35:31 -05:00

jccolext-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jccolor-altivec.c

AltiVec SIMD implementation of YCC-to-RGB color conversion

2015-01-10 22:56:26 +00:00

jccolor-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jccolor-sse2-64.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jccolor-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jcgray-altivec.c

AltiVec SIMD implementation of YCC-to-RGB color conversion

2015-01-10 22:56:26 +00:00

jcgray-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jcgray-sse2-64.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jcgray-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jcgryext-altivec.c

Extend the AltiVec VMX SIMD routines to support little endian PowerPC platforms.

2015-02-20 19:57:21 +00:00

jcgryext-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jcgryext-sse2-64.asm

Fix x86-64 ABI conformance issue in SIMD code

2015-09-16 22:35:31 -05:00

jcgryext-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jchuff-sse2-64.asm

SSE2 SIMD implementation of Huffman encoding

2016-01-12 03:03:49 -06:00

jchuff-sse2.asm

SSE2 SIMD implementation of Huffman encoding

2016-01-12 03:03:49 -06:00

jcolsamp.inc

Add SSE2 SIMD implementation of computationally intensive routines.

2009-03-09 13:34:17 +00:00

jcsample-altivec.c

Extend the AltiVec VMX SIMD routines to support little endian PowerPC platforms.

2015-02-20 19:57:21 +00:00

jcsample-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jcsample-sse2-64.asm

Fix x86-64 ABI conformance issue in SIMD code

2015-09-16 22:35:31 -05:00

jcsample-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jcsample.h

Rename README, LICENSE, BUILDING text files

2015-10-10 10:31:33 -05:00

jdcolext-altivec.c

Extend the AltiVec VMX SIMD routines to support little endian PowerPC platforms.

2015-02-20 19:57:21 +00:00

jdcolext-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jdcolext-sse2-64.asm

Fix x86-64 ABI conformance issue in SIMD code

2015-09-16 22:35:31 -05:00

jdcolext-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jdcolor-altivec.c

AltiVec SIMD implementation of YCC-to-RGB color conversion

2015-01-10 22:56:26 +00:00

jdcolor-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jdcolor-sse2-64.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jdcolor-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jdct.inc

Convert tabs to spaces in the libjpeg code and the SIMD code (TurboJPEG retains the use of tabs for historical reasons. They were annoying in the libjpeg code primarily because they were not consistently used and because they were used to format as well as indent the code. In the case of TurboJPEG, tabs are used just to indent the code, so even if the editor assumes a different tab width, the code will still be readable.)

2014-05-09 18:00:32 +00:00

jdmerge-altivec.c

AltiVec SIMD implementation of H2V1 and H2V2 merged upsampling

2015-01-14 13:27:32 +00:00

jdmerge-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jdmerge-sse2-64.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jdmerge-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jdmrgext-altivec.c

Extend the AltiVec VMX SIMD routines to support little endian PowerPC platforms.

2015-02-20 19:57:21 +00:00

jdmrgext-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jdmrgext-sse2-64.asm

Fix x86-64 ABI conformance issue in SIMD code

2015-09-16 22:35:31 -05:00

jdmrgext-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jdsample-altivec.c

Extend the AltiVec VMX SIMD routines to support little endian PowerPC platforms.

2015-02-20 19:57:21 +00:00

jdsample-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jdsample-sse2-64.asm

Fix x86-64 ABI conformance issue in SIMD code

2015-09-16 22:35:31 -05:00

jdsample-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jfdctflt-3dn.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jfdctflt-sse-64.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jfdctflt-sse.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jfdctfst-altivec.c

Make the formatting and naming of variables and constants more consistent

2015-01-13 10:00:12 +00:00

jfdctfst-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jfdctfst-sse2-64.asm

Revert r1335 and r1336. It was a valiant effort, but on Windows, xmm8-xmm15 are non-volatile, and the overhead of pushing them onto the stack at the beginning of each function and popping them at the end was causing worse performance (in the neighborhood of 3-5%) than just using the work areas and limiting the register usage to xmm0-xmm7. Best to leave the SSE2 code alone. We can optimize the register usage for AVX2, once that port takes place.

2014-08-22 18:30:44 +00:00

jfdctfst-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jfdctint-altivec.c

Revert r1506 (we actually are generating columns with the IDCT, so the naming makes sense in retrospect); further de-confusification in the forward DCT

2015-01-16 03:13:16 +00:00

jfdctint-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jfdctint-sse2-64.asm

Revert r1335 and r1336. It was a valiant effort, but on Windows, xmm8-xmm15 are non-volatile, and the overhead of pushing them onto the stack at the beginning of each function and popping them at the end was causing worse performance (in the neighborhood of 3-5%) than just using the work areas and limiting the register usage to xmm0-xmm7. Best to leave the SSE2 code alone. We can optimize the register usage for AVX2, once that port takes place.

2014-08-22 18:30:44 +00:00

jfdctint-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jidctflt-3dn.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jidctflt-sse2-64.asm

Fix x86-64 ABI conformance issue in SIMD code

2015-09-16 22:35:31 -05:00

jidctflt-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jidctflt-sse.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jidctfst-altivec.c

Revert r1506 (we actually are generating columns with the IDCT, so the naming makes sense in retrospect); further de-confusification in the forward DCT

2015-01-16 03:13:16 +00:00

jidctfst-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jidctfst-sse2-64.asm

Fix x86-64 ABI conformance issue in SIMD code

2015-09-16 22:35:31 -05:00

jidctfst-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jidctint-altivec.c

Revert r1506 (we actually are generating columns with the IDCT, so the naming makes sense in retrospect); further de-confusification in the forward DCT

2015-01-16 03:13:16 +00:00

jidctint-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jidctint-sse2-64.asm

Fix x86-64 ABI conformance issue in SIMD code

2015-09-16 22:35:31 -05:00

jidctint-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jidctred-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jidctred-sse2-64.asm

Fix x86-64 ABI conformance issue in SIMD code

2015-09-16 22:35:31 -05:00

jidctred-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jpeg_nbits_table.inc

SSE2 SIMD implementation of Huffman encoding

2016-01-12 03:03:49 -06:00

jquant-3dn.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jquant-mmx.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jquant-sse.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jquantf-sse2-64.asm

Fix x86-64 ABI conformance issue in SIMD code

2015-09-16 22:35:31 -05:00

jquantf-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jquanti-altivec.c

Extend the AltiVec VMX SIMD routines to support little endian PowerPC platforms.

2015-02-20 19:57:21 +00:00

jquanti-sse2-64.asm

Fix x86-64 ABI conformance issue in SIMD code

2015-09-16 22:35:31 -05:00

jquanti-sse2.asm

Using subdirectories unfortunately opened up a can of worms. In order to prevent object name conflicts, it is necessary to use the subdir-objects automake directive, but it simply doesn't work right on some of the versions of automake we still have to support. Another option would be to add a separate Makefile.am file to each subdirectory, but that requires maintaining a completely different set of build rules for each one. Fortunately, however, we're in the 21st century now, so we can use filenames longer than 8.3.

2014-05-10 09:53:34 +00:00

jsimd_altivec.h

Extend the AltiVec VMX SIMD routines to support little endian PowerPC platforms.

2015-02-20 19:57:21 +00:00

jsimd_arm64_neon.S

Optimize ARM64 SIMD code for Cavium ThunderX

2016-01-16 02:39:02 -06:00

jsimd_arm64.c

Complete the ARM64 NEON SIMD implementation

2016-01-15 11:21:48 -06:00

jsimd_arm_neon.S

ARM32 NEON SIMD implementation of Huffman encoding

2016-01-13 23:38:35 -06:00

jsimd_arm.c

Add JSIMD_NOHUFFENC environment variable for ARM

2016-01-15 13:15:54 -06:00

jsimd_i386.c

SSE2 SIMD implementation of Huffman encoding

2016-01-12 03:03:49 -06:00

jsimd_mips_dspr2_asm.h

SIMD-accelerated floating point quantize and convsamp routines for MIPS DSPr2

2013-10-09 18:39:44 +00:00

jsimd_mips_dspr2.S

Replace INT32 with a new internal datatype (JLONG)

2015-10-14 20:34:32 -05:00

jsimd_mips.c

SSE2 SIMD implementation of Huffman encoding

2016-01-12 03:03:49 -06:00

jsimd_powerpc.c

SSE2 SIMD implementation of Huffman encoding

2016-01-12 03:03:49 -06:00

jsimd_x86_64.c

SSE2 SIMD implementation of Huffman encoding

2016-01-12 03:03:49 -06:00

jsimd.h

Complete the ARM64 NEON SIMD implementation

2016-01-15 11:21:48 -06:00

jsimdcfg.inc.h

Remove MS-DOS code and information, and adjust copyright headers to reflect the removal of features in r1307 and r1308. libjpeg-turbo has never supported MS-DOS, nor is it even possible for us to do so.

2014-05-18 18:33:44 +00:00

jsimdcpu.asm

Convert tabs to spaces in the libjpeg code and the SIMD code (TurboJPEG retains the use of tabs for historical reasons. They were annoying in the libjpeg code primarily because they were not consistently used and because they were used to format as well as indent the code. In the case of TurboJPEG, tabs are used just to indent the code, so even if the editor assumes a different tab width, the code will still be readable.)

2014-05-09 18:00:32 +00:00

jsimdext.inc

Add proper support for Borland compilers (Borland needs section names to be prefixed with an underscore, and it needs OMF object files.)

2014-06-22 21:14:39 +00:00

Makefile.am

SSE2 SIMD implementation of Huffman encoding

2016-01-12 03:03:49 -06:00

nasm_lt.sh

Enable silent build rules for the NASM objects, if the source is configured with automake 1.11 or later. NOTE: the build still spits out "error: ignoring unknown tag NASM" for each object, but unfortunately, if we remove "--tag NASM" from the command line, the build breaks under older versions of automake (it aborts with "unable to infer tagged configuration.")

2015-02-23 19:03:29 +00:00