Go to the documentation of this file.
28 memset(
block, 0,
sizeof(int16_t) * 64);
33 memset(blocks, 0,
sizeof(int16_t) * 6 * 64);
41 for (
i = 0;
i <
h;
i++) {
52 for (
i = 0;
i <
h;
i++) {
void ff_blockdsp_init_mips(BlockDSPContext *c)
void ff_blockdsp_init_x86(BlockDSPContext *c)
av_cold void ff_blockdsp_init(BlockDSPContext *c)
av_cold void ff_blockdsp_init_arm(BlockDSPContext *c)
static void clear_blocks_c(int16_t *blocks)
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
#define i(width, name, range_min, range_max)
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
static void fill_block16_c(uint8_t *block, uint8_t value, ptrdiff_t line_size, int h)
av_cold void ff_blockdsp_init_ppc(BlockDSPContext *c)
static void clear_block_c(int16_t *block)
void ff_blockdsp_init_riscv(BlockDSPContext *c)
The exact code depends on how similar the blocks are and how related they are to the block
static void fill_block8_c(uint8_t *block, uint8_t value, ptrdiff_t line_size, int h)