Go to the documentation of this file.
30 const uint8_t *s2, ptrdiff_t
stride);
37 const uint8_t *s2, ptrdiff_t
stride);
39 const uint8_t *s2, ptrdiff_t
stride);
43 unsigned high_bit_depth)
54 if (!high_bit_depth) {
av_cold void ff_pixblockdsp_init_arm(PixblockDSPContext *c, AVCodecContext *avctx, unsigned high_bit_depth)
void ff_get_pixels_neon(int16_t *block, const uint8_t *pixels, ptrdiff_t stride)
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
static atomic_int cpu_flags
void ff_get_pixels_unaligned_neon(int16_t *block, const uint8_t *pixels, ptrdiff_t stride)
void ff_get_pixels_armv6(int16_t *block, const uint8_t *pixels, ptrdiff_t stride)
Undefined Behavior In the C some operations are like signed integer dereferencing freed accessing outside allocated Undefined Behavior must not occur in a C it is not safe even if the output of undefined operations is unused The unsafety may seem nit picking but Optimizing compilers have in fact optimized code on the assumption that no undefined Behavior occurs Optimizing code based on wrong assumptions can and has in some cases lead to effects beyond the output of computations The signed integer overflow problem in speed critical code Code which is highly optimized and works with signed integers sometimes has the problem that often the output of the computation does not c
void ff_diff_pixels_armv6(int16_t *block, const uint8_t *s1, const uint8_t *s2, ptrdiff_t stride)
main external API structure.
void ff_diff_pixels_unaligned_neon(int16_t *block, const uint8_t *s1, const uint8_t *s2, ptrdiff_t stride)
#define have_armv6(flags)
The exact code depends on how similar the blocks are and how related they are to the block
void ff_diff_pixels_neon(int16_t *block, const uint8_t *s1, const uint8_t *s2, ptrdiff_t stride)