void ff_fill_block8_mmi(uint8_t *block, uint8_t value, ptrdiff_t line_size, int h)
void ff_fill_block16_mmi(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_block16_msa(uint8_t *src, uint8_t val, ptrdiff_t stride, int height)
void ff_clear_blocks_mmi(int16_t *block)
void ff_clear_blocks_msa(int16_t *block)
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_clear_block_mmi(int16_t *block)
void ff_fill_block8_msa(uint8_t *src, uint8_t val, ptrdiff_t stride, int height)
void ff_clear_block_msa(int16_t *block)
void ff_blockdsp_init_mips(BlockDSPContext *c)