Go to the documentation of this file.
31 const float (*
filter)[8][2], ptrdiff_t,
int n);
38 float h[2][4],
float h_step[2][4],
int len);
void ff_ps_add_squares_rvv(float *dst, const float(*src)[2], int n)
void(* filter)(uint8_t *src, int stride, int qscale)
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
void ff_ps_stereo_interpolate_rvv(float(*l)[2], float(*r)[2], float h[2][4], float h_step[2][4], int len)
#define AV_CPU_FLAG_RVB
B (bit manipulations)
void ff_ps_hybrid_analysis_ileave_rvv(float(*out)[32][2], float L[2][38][64], int i, int len)
#define AV_CPU_FLAG_RVV_F32
Vectors of float's */.
av_cold void ff_psdsp_init_riscv(PSDSPContext *c)
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
uint8_t ptrdiff_t const uint8_t ptrdiff_t int intptr_t intptr_t int int16_t * dst
#define i(width, name, range_min, range_max)
void ff_ps_hybrid_analysis_rvv(float(*out)[2], float(*in)[2], const float(*filter)[8][2], ptrdiff_t, int n)
#define AV_CPU_FLAG_RVV_I32
Vectors of 8/16/32-bit int's */.
#define flags(name, subs,...)
void ff_ps_hybrid_synthesis_deint_rvv(float out[2][38][64], float(*in)[32][2], int i, int len)
void ff_ps_mul_pair_single_rvv(float(*dst)[2], float(*src0)[2], float *src1, int n)
#define AV_CPU_FLAG_RVV_I64
Vectors of 64-bit int's */.