Go to the documentation of this file.
31 #define randomize_buffers(buf, size) \
34 for (j = 0; j < size; j++) \
35 buf[j] = rnd() & 0xFFFF; \
47 if (!
src0 || !
src1 || !dst0 || !dst1)
56 if (memcmp(dst0, dst1,
width *
sizeof(uint16_t)))
76 report(
"add_int16_rnd_width");
it s the only field you need to keep assuming you have a context There is some magic you don t need to care about around this just let it vf default minimum maximum flags name is the option name
#define check_func(func,...)
void checkasm_check_huffyuvdsp(void)
static const uint16_t mask[17]
static void check_add_int16(HuffYUVDSPContext c, unsigned mask, int width, const char *name)
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
av_cold void ff_huffyuvdsp_init(HuffYUVDSPContext *c, enum AVPixelFormat pix_fmt)
#define randomize_buffers(buf, size)
void * av_mallocz(size_t size)
Allocate a memory block with alignment suitable for all memory accesses (including vectors if availab...
@ AV_PIX_FMT_YUV422P
planar YUV 4:2:2, 16bpp, (1 Cr & Cb sample per 2x1 Y samples)
#define declare_func(ret,...)