DRC bd49803f92 Use consistent/modern code formatting for pointers ...

The convention used by libjpeg:

    type * variable;

is not very common anymore, because it looks too much like
multiplication.  Some (particularly C++ programmers) prefer to tuck the
pointer symbol against the type:

    type* variable;

to emphasize that a pointer to a type is effectively a new type.
However, this can also be confusing, since defining multiple variables
on the same line would not work properly:

    type* variable1, variable2;  /* Only variable1 is actually a
                                    pointer. */

This commit reformats the entirety of the libjpeg-turbo code base so
that it uses the same code formatting convention for pointers that the
TurboJPEG API code uses:

    type *variable1, *variable2;

This seems to be the most common convention among C programmers, and
it is the convention used by other codec libraries, such as libpng and
libtiff.

2016-02-19 09:10:07 -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

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jchuff-sse2.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -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

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jdsample-mmx.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jdsample-sse2-64.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jdsample-sse2.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jfdctflt-3dn.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jfdctflt-sse-64.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jfdctflt-sse.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06: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

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jfdctfst-sse2-64.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jfdctfst-sse2.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06: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

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jfdctint-sse2-64.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jfdctint-sse2.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctflt-3dn.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctflt-sse2-64.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctflt-sse2.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctflt-sse.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctfst-altivec.c

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctfst-mmx.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctfst-sse2-64.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctfst-sse2.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctint-altivec.c

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctint-mmx.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctint-sse2-64.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctint-sse2.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctred-mmx.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctred-sse2-64.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jidctred-sse2.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jpeg_nbits_table.inc

SSE2 SIMD implementation of Huffman encoding

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

jquant-3dn.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jquant-mmx.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jquant-sse.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jquantf-sse2-64.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jquantf-sse2.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jquanti-altivec.c

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jquanti-sse2-64.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jquanti-sse2.asm

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06: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

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jsimd_arm64.c

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jsimd_arm_neon.S

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jsimd_arm.c

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jsimd_i386.c

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -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

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jsimd_powerpc.c

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jsimd_x86_64.c

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -06:00

jsimd.h

Use consistent/modern code formatting for pointers

2016-02-19 09:10:07 -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

Fix 'make dist'; Include LICENSE.md in packages

2016-02-08 14:03:13 -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