Go to the documentation of this file.
28 #define bf(fn, bd, opt) fn##_##bd##_##opt
30 #define AVG_PROTOTYPES(bd, opt) \
31 void bf(ff_vvc_avg, bd, opt)(uint8_t *dst, ptrdiff_t dst_stride, \
32 const int16_t *src0, const int16_t *src1, int width, int height); \
33 void bf(ff_vvc_w_avg, bd, opt)(uint8_t *dst, ptrdiff_t dst_stride, \
34 const int16_t *src0, const int16_t *src1, int width, int height, \
35 int denom, int w0, int w1, int o0, int o1);
49 vlenb = ff_get_rv_vlenb();
53 c->inter.avg = ff_vvc_avg_8_rvv_256;
54 # if (__riscv_xlen == 64)
55 c->inter.w_avg = ff_vvc_w_avg_8_rvv_256;
61 }
else if (vlenb >= 16) {
64 c->inter.avg = ff_vvc_avg_8_rvv_128;
65 # if (__riscv_xlen == 64)
66 c->inter.w_avg = ff_vvc_w_avg_8_rvv_128;
#define AVG_PROTOTYPES(bd, opt)
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
#define AV_CPU_FLAG_RVB
B (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 */.
void ff_vvc_dsp_init_riscv(VVCDSPContext *const c, const int bd)
#define flags(name, subs,...)