#define EXTERNAL_AVX2_FAST(flags)
void ff_rct_int_sse2(void *src0, void *src1, void *src2, int csize)
av_cold void ff_jpeg2000dsp_init_x86(Jpeg2000DSPContext *c)
void ff_ict_float_avx(void *src0, void *src1, void *src2, int csize)
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
void ff_ict_float_fma3(void *src0, void *src1, void *src2, int csize)
static atomic_int cpu_flags
void ff_rct_int_avx2(void *src0, void *src1, void *src2, int csize)
void ff_ict_float_fma4(void *src0, void *src1, void *src2, int csize)
#define EXTERNAL_SSE(flags)
#define EXTERNAL_AVX_FAST(flags)
#define EXTERNAL_FMA4(flags)
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
void ff_ict_float_sse(void *src0, void *src1, void *src2, int csize)
#define EXTERNAL_SSE2(flags)
#define EXTERNAL_FMA3_FAST(flags)