Go to the documentation of this file.
27 int16_t *low, ptrdiff_t low_stride,
28 int16_t *high, ptrdiff_t high_stride,
33 4 *
input[2*in_stride] + 4 *
input[3*in_stride] -
34 1 *
input[4*in_stride] - 1 *
input[5*in_stride] + 4) >> 3);
36 for (
int i = 2;
i <
len - 2;
i += 2) {
39 input[(
i+2)*in_stride] +
input[(
i+3)*in_stride] + 4) >> 3) +
46 1 *
input[((
len-2)-3)*in_stride] + 1 *
input[((
len-2)-4)*in_stride] + 4) >> 3);
50 ptrdiff_t in_stride, ptrdiff_t low_stride,
51 ptrdiff_t high_stride,
63 ptrdiff_t in_stride, ptrdiff_t low_stride,
64 ptrdiff_t high_stride,
static void vert_filter(int16_t *input, int16_t *low, int16_t *high, ptrdiff_t in_stride, ptrdiff_t low_stride, ptrdiff_t high_stride, int width, int height)
void ff_cfhdencdsp_init_x86(CFHDEncDSPContext *c)
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
and forward the test the status of outputs and forward it to the corresponding return FFERROR_NOT_READY If the filters stores internally one or a few frame for some input
#define i(width, name, range_min, range_max)
av_cold void ff_cfhdencdsp_init(CFHDEncDSPContext *c)
static void horiz_filter(int16_t *input, int16_t *low, int16_t *high, ptrdiff_t in_stride, ptrdiff_t low_stride, ptrdiff_t high_stride, int width, int height)
static av_always_inline void filter(int16_t *input, ptrdiff_t in_stride, int16_t *low, ptrdiff_t low_stride, int16_t *high, ptrdiff_t high_stride, int len)