Go to the documentation of this file.
49 res += *v1 * (uint32_t)*v2++;
51 res += *v1 * (uint32_t)*v2++;
av_cold void ff_llauddsp_init(LLAudDSPContext *c)
void ff_llauddsp_init_riscv(LLAudDSPContext *c)
static int32_t scalarproduct_and_madd_int16_c(int16_t *v1, const int16_t *v2, const int16_t *v3, int order, int mul)
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_llauddsp_init_x86(LLAudDSPContext *c)
static int32_t scalarproduct_and_madd_int32_c(int16_t *v1, const int32_t *v2, const int16_t *v3, int order, int mul)
av_cold void ff_llauddsp_init_arm(LLAudDSPContext *c)
void ff_llauddsp_init_ppc(LLAudDSPContext *c)