Go to the documentation of this file.
29 int beta, int8_t *tc0);
31 int beta, int8_t *tc0);
33 int beta, int8_t *tc0);
35 int beta, int8_t *tc0);
37 int beta, int8_t *tc0);
47 int height,
int log2_den,
int weightd,
50 int height,
int log2_den,
int weightd,
53 int height,
int log2_den,
int weightd,
75 const int chroma_format_idc)
83 if (chroma_format_idc <= 1)
100 if (chroma_format_idc <= 1)
110 const int chroma_format_idc)
static void bit_depth(AudioStatsContext *s, uint64_t mask, uint64_t imask, AVRational *depth)
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
void ff_h264_v_loop_filter_luma_neon(uint8_t *pix, ptrdiff_t stride, int alpha, int beta, int8_t *tc0)
static atomic_int cpu_flags
void ff_biweight_h264_pixels_16_neon(uint8_t *dst, uint8_t *src, int stride, int height, int log2_den, int weightd, int weights, int offset)
void ff_h264_h_loop_filter_luma_neon(uint8_t *pix, ptrdiff_t stride, int alpha, int beta, int8_t *tc0)
av_cold void ff_h264dsp_init_arm(H264DSPContext *c, const int bit_depth, const int chroma_format_idc)
void ff_h264_idct_add8_neon(uint8_t **dest, const int *block_offset, int16_t *block, int stride, const uint8_t nnzc[6 *8])
void ff_h264_h_loop_filter_chroma422_neon(uint8_t *pix, ptrdiff_t stride, int alpha, int beta, int8_t *tc0)
void ff_h264_idct_dc_add_neon(uint8_t *dst, int16_t *block, int stride)
void ff_h264_idct8_add4_neon(uint8_t *dst, const int *block_offset, int16_t *block, int stride, const uint8_t nnzc[6 *8])
void ff_biweight_h264_pixels_4_neon(uint8_t *dst, uint8_t *src, int stride, int height, int log2_den, int weightd, int weights, int offset)
void ff_h264_idct8_add_neon(uint8_t *dst, int16_t *block, int stride)
void ff_weight_h264_pixels_16_neon(uint8_t *dst, int stride, int height, int log2_den, int weight, int offset)
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
static int weight(int i, int blen, int offset)
void ff_h264_idct_add16intra_neon(uint8_t *dst, const int *block_offset, int16_t *block, int stride, const uint8_t nnzc[6 *8])
Context for storing H.264 DSP functions.
int ff_startcode_find_candidate_armv6(const uint8_t *buf, int size)
void ff_h264_v_loop_filter_chroma_neon(uint8_t *pix, ptrdiff_t stride, int alpha, int beta, int8_t *tc0)
void ff_weight_h264_pixels_4_neon(uint8_t *dst, int stride, int height, int log2_den, int weight, int offset)
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 offset
static av_cold void h264dsp_init_neon(H264DSPContext *c, const int bit_depth, const int chroma_format_idc)
void ff_h264_idct_add_neon(uint8_t *dst, int16_t *block, int stride)
void ff_h264_idct_add16_neon(uint8_t *dst, const int *block_offset, int16_t *block, int stride, const uint8_t nnzc[6 *8])
void ff_h264_idct8_dc_add_neon(uint8_t *dst, int16_t *block, int stride)
#define have_setend(flags)
static const int16_t alpha[]
The exact code depends on how similar the blocks are and how related they are to the block
void ff_weight_h264_pixels_8_neon(uint8_t *dst, int stride, int height, int log2_den, int weight, int offset)
void ff_h264_h_loop_filter_chroma_neon(uint8_t *pix, ptrdiff_t stride, int alpha, int beta, int8_t *tc0)
void ff_biweight_h264_pixels_8_neon(uint8_t *dst, uint8_t *src, int stride, int height, int log2_den, int weightd, int weights, int offset)