First pass at an Android makefile


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1265 632fc199-4ca6-4c93-a231-07263d6284db
Redesign the libjpeg regression tests so that they fully cover all of the SIMD-accelerated algorithms (and most of the other ones as well)


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1267 632fc199-4ca6-4c93-a231-07263d6284db
Phrasing.  Boom.


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1268 632fc199-4ca6-4c93-a231-07263d6284db
SIMD-accelerated slow integer IDCT routine for MIPS DSPr2


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1269 632fc199-4ca6-4c93-a231-07263d6284db
Wordsmithing


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1270 632fc199-4ca6-4c93-a231-07263d6284db
Replace our custom version of Android.mk with instructions on how to build a libjpeg-turbo SDK for Android using autotools.  Upon consulting with AOSP, it appears that Android.mk isn't really necessary except when building libjpeg-turbo for use by the Android platform itself, and it makes more sense for them to maintain the makefile for that purpose rather than for it to be upstreamed.  ndk-build has serious limitations that prevent it from being used to generate static libjpeg-turbo libraries (mainly, it isn't possible to combine pre-built objects from one module into a static library for another module, which is necessary because the SIMD extensions sometimes have to be built with different CFLAGS than the rest of the code.)  In general, it's just better not to introduce a new build system.


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1272 632fc199-4ca6-4c93-a231-07263d6284db
Redesign the libjpeg regression tests so that they fully cover all of the SIMD-accelerated algorithms (and most of the other ones as well)


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1274 632fc199-4ca6-4c93-a231-07263d6284db
Shared the rm commands to reduce as much output noise as possible


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1275 632fc199-4ca6-4c93-a231-07263d6284db
Fix regression that caused 'make test' to fail with non-x86 SIMD code.  The round-off error in the SIMD float DCT/IDCT routines only exists in the SSE and SSE2 implementations.


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1276 632fc199-4ca6-4c93-a231-07263d6284db
Fix an error in the MIPS DSPr2 fancy upsampling routine


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1277 632fc199-4ca6-4c93-a231-07263d6284db
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.)


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1278 632fc199-4ca6-4c93-a231-07263d6284db
Remove trailing spaces (+ one additional tab in TJUnitTest.java that was missed in the previous commit)


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1279 632fc199-4ca6-4c93-a231-07263d6284db
Re-organize the x86/x86-64 SIMD routines into separate folders by instruction set so we can name each routine similarly to its corresponding C file.  This also makes it easier to add support for new instruction sets.


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1280 632fc199-4ca6-4c93-a231-07263d6284db
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.


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1282 632fc199-4ca6-4c93-a231-07263d6284db
Modify Windows build system to take into account new assembly file names


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1283 632fc199-4ca6-4c93-a231-07263d6284db
Provide a more thorough description of the trade-offs between the various DCT/IDCT algorithms, based on new resarch


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1287 632fc199-4ca6-4c93-a231-07263d6284db
Port the more accurate (and slightly faster) floating point IDCT implementation from jpeg-8a and later.  New research revealed that the SSE/SSE2 floating point IDCT implementation was actually more accurate than the jpeg-6b implementation, not less, which is why its mathematical results have always differed from those of the jpeg-6b implementation.  This patch brings the accuracy of the C code in line with that of the SSE/SSE2 code.


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1288 632fc199-4ca6-4c93-a231-07263d6284db
Document the fact that the fast integer FDCT is not fully accelerated for quality levels above 97 + additional wordsmithing


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1290 632fc199-4ca6-4c93-a231-07263d6284db
Use 2-space indentation for the enums, to be consistent with the structs


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1292 632fc199-4ca6-4c93-a231-07263d6284db
Document -rgb option in djpeg man page;  "gray-scale"="grayscale"


git-svn-id: svn://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1294 632fc199-4ca6-4c93-a231-07263d6284db