Go to the documentation of this file.
60 c->sum_square_butterfly_float =
63 # if __riscv_xlen >= 64
65 c->sum_square_butterfly_int32 =
void ff_sum_square_butterfly_float_rvv(float *, const float *, const float *, int)
static int nb_coefs(int length, int level, uint64_t sn)
#define AV_CPU_FLAG_RVB_BASIC
Basic bit-manipulations.
#define AV_CPU_FLAG_RV_ZVBB
Vector basic bit-manipulations.
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
#define AV_CPU_FLAG_RVB
B (bit manipulations)
void ff_float_to_fixed24_rvv(int32_t *dst, const float *src, size_t len)
#define AV_CPU_FLAG_RVV_F32
Vectors of float's */.
void ff_extract_exponents_rvb(uint8_t *exp, int32_t *coef, int nb_coefs)
void ff_ac3_exponent_min_rvb(uint8_t *exp, int, int)
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
void ff_sum_square_butterfly_int32_rvv(int64_t *, const int32_t *, const int32_t *, int)
av_cold void ff_ac3dsp_init_riscv(AC3DSPContext *c)
#define AV_CPU_FLAG_RVV_I32
Vectors of 8/16/32-bit int's */.
void ff_ac3_exponent_min_rvv(uint8_t *exp, int, int)
void ff_extract_exponents_rvvb(uint8_t *exp, int32_t *coef, int nb_coefs)
#define flags(name, subs,...)
#define AV_CPU_FLAG_RVV_I64
Vectors of 64-bit int's */.