Go to the documentation of this file.
33 #if HAVE_RVV && (__riscv_xlen >= 64)
39 if (ff_get_rv_vlenb() >
c->max_order)
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
#define AV_CPU_FLAG_RVV_F64
Vectors of double's.
#define AV_CPU_FLAG_RVB_ADDR
Address bit-manipulations.
void ff_lpc_compute_autocorr_rvv(const double *, ptrdiff_t, int, double *)
void ff_lpc_apply_welch_window_rvv(const int32_t *, ptrdiff_t, double *)
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
av_cold void ff_lpc_init_riscv(LPCContext *c)
#define flags(name, subs,...)