Go to the documentation of this file.
31 static void vorbis_inverse_coupling_altivec(
float *mag,
float *ang,
36 vector
bool int t0,
t1;
37 const vector
unsigned int v_31 =
38 vec_add(vec_add(vec_splat_u32(15),vec_splat_u32(15)),vec_splat_u32(1));
39 for (
i = 0;
i < blocksize;
i += 4) {
42 t0 = vec_cmple(m, (vector
float)vec_splat_u32(0));
43 t1 = vec_cmple(
a, (vector
float)vec_splat_u32(0));
44 a = vec_xor(
a, (vector
float) vec_sl((vector
unsigned int)
t0, v_31));
45 t0 = (vector
bool int)vec_and(
a,
t1);
46 t1 = (vector
bool int)vec_andc(
a,
t1);
47 a = vec_sub(m, (vector
float)
t1);
48 m = vec_add(m, (vector
float)
t0);
61 c->vorbis_inverse_coupling = vorbis_inverse_coupling_altivec;
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
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)
The reader does not expect b to be semantically here and if the code is changed by maybe adding a a division or other the signedness will almost certainly be mistaken To avoid this confusion a new type was SUINT is the C unsigned type but it holds a signed int to use the same example SUINT a
#define i(width, name, range_min, range_max)
av_cold void ff_vorbisdsp_init_ppc(VorbisDSPContext *c)