29 #define YUV2RGB_LOOP(depth) \ 30 h_size = (c->dstW + 7) & ~7; \ 31 if (h_size * depth > FFABS(dstStride[0])) \ 34 vshift = c->srcFormat != AV_PIX_FMT_YUV422P; \ 36 for (y = 0; y < srcSliceH; y++) { \ 37 uint8_t *image = dst[0] + (y + srcSliceY) * dstStride[0]; \ 38 const uint8_t *py = src[0] + y * srcStride[0]; \ 39 const uint8_t *pu = src[1] + (y >> vshift) * srcStride[1]; \ 40 const uint8_t *pv = src[2] + (y >> vshift) * srcStride[2]; \ 41 x86_reg index = -h_size / 2; \ 44 const uint8_t *pv_index,
const uint64_t *pointer_c_dither,
47 const uint8_t *pv_index,
const uint64_t *pointer_c_dither,
50 #if !COMPILE_TEMPLATE_MMXEXT 52 const uint8_t *pv_index,
const uint64_t *pointer_c_dither,
55 const uint8_t *pv_index,
const uint64_t *pointer_c_dither,
58 const uint8_t *pv_index,
const uint64_t *pointer_c_dither,
61 const uint8_t *pv_index,
const uint64_t *pointer_c_dither,
64 const uint8_t *pv_index,
const uint64_t *pointer_c_dither,
67 const uint8_t *pv_index,
const uint64_t *pointer_c_dither,
73 uint8_t *dst[],
int dstStride[])
75 int y, h_size, vshift;
93 uint8_t *dst[],
int dstStride[])
95 int y, h_size, vshift;
113 uint8_t *dst[],
int dstStride[])
115 int y, h_size, vshift;
127 uint8_t *dst[],
int dstStride[])
129 int y, h_size, vshift;
141 uint8_t *dst[],
int dstStride[])
143 int y, h_size, vshift;
146 const uint8_t *pa =
src[3] + y * srcStride[3];
155 uint8_t *dst[],
int dstStride[])
157 int y, h_size, vshift;
161 const uint8_t *pa =
src[3] + y * srcStride[3];
171 uint8_t *dst[],
int dstStride[])
173 int y, h_size, vshift;
185 uint8_t *dst[],
int dstStride[])
187 int y, h_size, vshift;
const uint64_t ff_dither8[2]
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
const uint64_t ff_dither4[2]
#define YUV2RGB_LOOP(depth)