void ff_fill_block_tab_16_avx2(uint8_t *block, uint8_t value, ptrdiff_t line_size, int h)
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
static atomic_int cpu_flags
void ff_fill_block_tab_8_avx2(uint8_t *block, uint8_t value, ptrdiff_t line_size, int h)
void ff_fill_block_tab_8_sse2(uint8_t *block, uint8_t value, ptrdiff_t line_size, int h)
#define EXTERNAL_AVX2(flags)
#define EXTERNAL_SSE(flags)
#define EXTERNAL_AVX_FAST(flags)
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_fill_block_tab_16_sse2(uint8_t *block, uint8_t value, ptrdiff_t line_size, int h)
#define EXTERNAL_SSE2(flags)
av_cold void ff_blockdsp_init_x86(BlockDSPContext *c)
void ff_clear_blocks_avx(int16_t *blocks)
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 value
void ff_clear_blocks_sse(int16_t *blocks)
void ff_clear_block_sse(int16_t *block)
The exact code depends on how similar the blocks are and how related they are to the block
void ff_clear_block_avx(int16_t *block)