Go to the documentation of this file.
46 #if HAVE_GNU_AS && HAVE_ALTIVEC && (HAVE_BIGENDIAN || HAVE_VSX)
50 int n = 1 <<
s->mdct_bits;
54 const uint16_t *revtabj =
s->revtab;
55 const uint16_t *revtabk =
s->revtab+n4;
64 vec_f cos,sin,cos0,sin0,cos1,sin1,
re,
im,r0,i0,r1,i1,
a,
b,
c,
d;
65 #define CMULA(p,o0,o1,o2,o3)\
68 re = vec_perm(a, b, vcprm(0,2,s0,s2)); \
69 im = vec_perm(a, b, vcprm(s3,s1,3,1)); \
70 cos = vec_perm(cos0, cos1, vcprm(o0,o1,s##o2,s##o3)); \
71 sin = vec_perm(sin0, sin1, vcprm(o0,o1,s##o2,s##o3));\
72 r##p = im*cos - re*sin;\
73 i##p = re*cos + im*sin;
74 #define STORE2(v,dst)\
76 vec_ste(v, 0, output+j*2);\
77 vec_ste(v, 4, output+j*2);
79 a = vec_perm(r##p, i##p, vcprm(0,s0,0,s0));\
80 b = vec_perm(r##p, i##p, vcprm(1,s1,1,s1));\
81 c = vec_perm(r##p, i##p, vcprm(2,s2,2,s2));\
82 d = vec_perm(r##p, i##p, vcprm(3,s3,3,s3));\
83 STORE2(a, revtabk[ p*2-4]);\
84 STORE2(b, revtabk[ p*2-3]);\
85 STORE2(c, revtabj[-p*2+2]);\
86 STORE2(d, revtabj[-p*2+3]);
112 #define CMULB(d0,d1,o)\
117 d0 = im*sin - re*cos;\
118 d1 = re*sin + im*cos;
122 pout[2*j] = vec_perm(
a,
d, vcprm(0,
s3,1,
s2));
123 pout[2*j+1] = vec_perm(
a,
d, vcprm(2,
s1,3,
s0));
124 pout[2*k] = vec_perm(
c,
b, vcprm(0,
s3,1,
s2));
125 pout[2*k+1] = vec_perm(
c,
b, vcprm(2,
s1,3,
s0));
134 int n = 1 <<
s->mdct_bits;
143 for (k = 0; k < n16; k++) {
146 p0[-k-1] = vec_perm(
a,
a, vcprm(3,2,1,0));
147 p1[k] = vec_perm(
b,
b, vcprm(3,2,1,0));
154 #if HAVE_GNU_AS && HAVE_ALTIVEC && (HAVE_BIGENDIAN || HAVE_VSX)
159 s->fft_calc = ff_fft_calc_interleave_vsx;
163 if (
s->mdct_bits >= 5) {
164 s->imdct_calc = imdct_calc_altivec;
165 s->imdct_half = imdct_half_altivec;
filter_frame For filters that do not use the this method is called when a frame is pushed to the filter s input It can be called at any time except in a reentrant way If the input frame is enough to produce output
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
void ff_fft_calc_interleave_altivec(FFTContext *s, FFTComplex *z)
av_cold void ff_fft_init_ppc(FFTContext *s)
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
and forward the test the status of outputs and forward it to the corresponding return FFERROR_NOT_READY If the filters stores internally one or a few frame for some input
void ff_fft_calc_altivec(FFTContext *s, FFTComplex *z)
Do a complex FFT with the parameters defined in ff_fft_init().