Bounty #2: use altivec to optimize the file x265/source/common/pixel.cpp

[Former user]

As a following action of ticket 137 (https://bitbucket.org/multicoreware/x265/issue/137/add-power-altivec-support-to-x265), there will be 3 bounties opened soon on bounty source to promote the altivec support in x265: https://www.bountysource.com/teams/ibm/bounties

Here is the summary of the second bounty: Use GCC altivec intrincics (https://gcc.gnu.org/onlinedocs/gcc/PowerPC-AltiVec_002fVSX-Built-in-Functions.html#PowerPC-AltiVec_002fVSX-Built-in-Functions) to optimize all of the functions in the x265/source/common/pixel.cpp. The result should be merged back to x265 open source software (http://x265.org/developers/). Estimated Price: 750USD

[John Comeau]

this may have already been done. I see a file source/common/ppc/altivec_pixel.cpp.

[John Comeau]

anyway, once I get my hands on a PPC instance I'll do some testing.

[John Comeau]

running with gdb, I set a breakpoint: (gdb) tbreak 'x265::satd_4x4_altivec(unsigned char const*, long, unsigned char const*, long)', and ran disas when it hit. for sure the altivec code was built into the shared library and is used by the x265 binary. this issue should be closed and the coders who wrote altivec_pixel.cpp should get the reward. if they don't wish to, or cannot because it would violate some terms of their participation, I'll be glad to take it for the time I invested.