19 #ifndef AVCODEC_H264CHROMA_H 20 #define AVCODEC_H264CHROMA_H void ff_h264chroma_init_arm(H264ChromaContext *c, int bit_depth)
h264_chroma_mc_func put_h264_chroma_pixels_tab[4]
void ff_h264chroma_init_ppc(H264ChromaContext *c, int bit_depth)
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(* h264_chroma_mc_func)(uint8_t *dst, uint8_t *src, ptrdiff_t srcStride, int h, int x, int y)
void ff_h264chroma_init(H264ChromaContext *c, int bit_depth)
typedef void(APIENTRY *FF_PFNGLACTIVETEXTUREPROC)(GLenum texture)
static void bit_depth(AudioStatsContext *s, uint64_t mask, uint64_t imask, AVRational *depth)
void ff_h264chroma_init_aarch64(H264ChromaContext *c, int bit_depth)
void ff_h264chroma_init_mips(H264ChromaContext *c, int bit_depth)
void ff_h264chroma_init_x86(H264ChromaContext *c, int bit_depth)
h264_chroma_mc_func avg_h264_chroma_pixels_tab[4]