Gitiles
Code Review
Sign In
gerrit-public.fairphone.software
/
platform
/
external
/
libjpeg-turbo
/
b2817f52517361caff3dbab7373abc1b791f3246
/
simd
/
jidctint-altivec.c
bd49803
Use consistent/modern code formatting for pointers
by DRC
· 9 years ago
246b01b
Revert r1506 (we actually are generating columns with the IDCT, so the naming makes sense in retrospect); further de-confusification in the forward DCT
by DRC
· 10 years ago
c4e3c36
De-confusify the variable names a bit -- "out" represents the output of the IDCT kernel, so use "final" to represent the packed data that will be stored to memory.
by DRC
· 10 years ago
a6a24c2
Make the formatting and naming of variables and constants more consistent
by DRC
· 10 years ago
d71a6e0
Use intrinsics for loading aligned data in the IDCT functions. This has no effect on performance, but it makes it more obvious what that code is doing.
by DRC
· 10 years ago
ff30c63
Document the fact that the AltiVec implementation uses the same modified algorithms as the SSE2 implementation
by DRC
· 10 years ago
4545308
Use intrinsics for loading/storing data in the DCT/IDCT functions. This has no effect on the performance of the aligned loads/stores, but it makes it more obvious what that code is doing. Using intrinsics for the unaligned stores in the inverse DCT functions increases overall decompression performance by 1-2%.
by DRC
· 10 years ago
13af139
Make comments more consistent
by DRC
· 10 years ago
535674b
Split AltiVec algorithms into separate files for ease of maintenance; Rename constants using lowercase so they are not confused with macros
by DRC
· 10 years ago