Go to the documentation of this file.
39 #define RVV_FNASSIGN(member, v, h, fn, ext) \
40 member[1][v][h] = ff_h2656_put_pixels_##8_##ext; \
41 member[3][v][h] = ff_h2656_put_pixels_##8_##ext; \
42 member[5][v][h] = ff_h2656_put_pixels_##8_##ext; \
43 member[7][v][h] = ff_h2656_put_pixels_##8_##ext; \
44 member[9][v][h] = ff_h2656_put_pixels_##8_##ext;
55 vlenb = ff_get_rv_vlenb();
65 }
else if (vlenb >= 16) {
void ff_hevc_add_residual_32x32_8_rvv(uint8_t *_dst, const int16_t *coeffs, ptrdiff_t stride)
static void bit_depth(AudioStatsContext *s, const uint64_t *const mask, uint8_t *depth)
#define RVV_FNASSIGN(member, v, h, fn, ext)
void ff_hevc_dsp_init_riscv(HEVCDSPContext *c, const int bit_depth)
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
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
void ff_hevc_add_residual_8x8_8_rvv(uint8_t *_dst, const int16_t *coeffs, ptrdiff_t stride)
void ff_hevc_add_residual_4x4_8_rvv(uint8_t *_dst, const int16_t *coeffs, ptrdiff_t stride)
#define AV_CPU_FLAG_RVV_I32
Vectors of 8/16/32-bit int's */.
#define AV_CPU_FLAG_RVB
B (bit manipulations)
void ff_hevc_add_residual_16x16_8_rvv(uint8_t *_dst, const int16_t *coeffs, ptrdiff_t stride)