Go to the documentation of this file.
28 const int16_t *v3,
int len,
31 const int16_t *v3,
int len,
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
#define AV_CPU_FLAG_RVB_ADDR
Address bit-manipulations.
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 AV_CPU_FLAG_RVV_I32
Vectors of 8/16/32-bit int's */.
int32_t ff_scalarproduct_and_madd_int16_rvv(int16_t *v1, const int16_t *v2, const int16_t *v3, int len, int mul)
av_cold void ff_llauddsp_init_riscv(LLAudDSPContext *c)
int32_t ff_scalarproduct_and_madd_int32_rvv(int16_t *v1, const int32_t *v2, const int16_t *v3, int len, int mul)
#define flags(name, subs,...)