Go to the documentation of this file.
31 #define GET_T(tt0,tt1,src,a,b){ \
32 a = vec_ld(16, src); \
33 tt0 = vec_perm(b, a, align); \
34 b = vec_ld(32, src); \
35 tt1 = vec_perm(a, b, align); \
38 #define GET_T(tt0,tt1,src,a,b){ \
39 tt0 = vec_vsx_ld(0, src); \
40 tt1 = vec_vsx_ld(16, src); \
45 static int32_t scalarproduct_and_madd_int16_altivec(int16_t *v1,
67 res = vec_msum(
t0, i0, res);
68 res = vec_msum(
t1, i1, res);
70 pv1[0] = vec_mladd(
t0, muls, i0);
71 pv1[1] = vec_mladd(
t1, muls, i1);
76 res = vec_splat(vec_sums(res,
zero_s32v), 3);
77 vec_ste(res, 0, &ires);
89 c->scalarproduct_and_madd_int16 = scalarproduct_and_madd_int16_altivec;
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
static float mul(float src0, float src1)
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 const uint8_t *BS_FUNC() align(BSCTX *bc)
Skip bits to a byte boundary.
av_cold void ff_llauddsp_init_ppc(LLAudDSPContext *c)
#define GET_T(tt0, tt1, src, a, b)