32 #define PUT_OP_U8_ALTIVEC(d, s, dst) d = s 33 #define AVG_OP_U8_ALTIVEC(d, s, dst) d = vec_avg(dst, s) 35 #define OP_U8_ALTIVEC PUT_OP_U8_ALTIVEC 36 #define PREFIX_h264_chroma_mc8_altivec put_h264_chroma_mc8_altivec 37 #define PREFIX_h264_chroma_mc8_num altivec_put_h264_chroma_mc8_num 38 #include "h264chroma_template.c" 40 #undef PREFIX_h264_chroma_mc8_altivec 41 #undef PREFIX_h264_chroma_mc8_num 43 #define OP_U8_ALTIVEC AVG_OP_U8_ALTIVEC 44 #define PREFIX_h264_chroma_mc8_altivec avg_h264_chroma_mc8_altivec 45 #define PREFIX_h264_chroma_mc8_num altivec_avg_h264_chroma_mc8_num 46 #include "h264chroma_template.c" 48 #undef PREFIX_h264_chroma_mc8_altivec 49 #undef PREFIX_h264_chroma_mc8_num 55 const int high_bit_depth = bit_depth > 8;
60 if (!high_bit_depth) {
av_cold void ff_h264chroma_init_ppc(H264ChromaContext *c, int bit_depth)
h264_chroma_mc_func put_h264_chroma_pixels_tab[4]
Macro definitions for various function/variable attributes.
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 PPC_ALTIVEC(flags)
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.
Contains misc utility macros and inline functions.
h264_chroma_mc_func avg_h264_chroma_pixels_tab[4]