#define EXTERNAL_AVX2_FAST(flags)
void ff_tak_decorrelate_ls_sse2(const int32_t *p1, int32_t *p2, int length)
void ff_tak_decorrelate_sf_sse4(int32_t *p1, const int32_t *p2, int length, int dshift, int dfactor)
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
static atomic_int cpu_flags
void ff_tak_decorrelate_sm_avx2(int32_t *p1, int32_t *p2, int length)
av_cold void ff_takdsp_init_x86(TAKDSPContext *c)
void ff_tak_decorrelate_sr_avx2(int32_t *p1, const int32_t *p2, int length)
void ff_tak_decorrelate_sm_sse2(int32_t *p1, int32_t *p2, int length)
void ff_tak_decorrelate_ls_avx2(const int32_t *p1, int32_t *p2, int length)
void ff_tak_decorrelate_sr_sse2(int32_t *p1, const int32_t *p2, int length)
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 EXTERNAL_SSE2(flags)
#define EXTERNAL_SSE4(flags)
void ff_tak_decorrelate_sf_avx2(int32_t *p1, const int32_t *p2, int length, int dshift, int dfactor)