Go to the documentation of this file.
29 ptrdiff_t
len,
int qscale,
int aic);
31 ptrdiff_t
len,
int qscale);
34 int16_t *
block,
int n,
int qscale)
37 block[0] *= (n < 4) ?
s->y_dc_scale :
s->c_dc_scale;
40 :
s->intra_scantable.raster_end[
s->block_last_index[n]];
45 int16_t *
block,
int n,
int qscale)
47 n =
s->inter_scantable.raster_end[
s->block_last_index[n]];
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_h263_dct_unquantize_inter_rvv(const MPVContext *s, int16_t *block, ptrdiff_t len, int qscale)
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 */.
av_cold void ff_mpv_unquantize_init_riscv(MPVUnquantDSPContext *c, int bitexact)
static void dct_unquantize_h263_inter_rvv(const MPVContext *s, int16_t *block, int n, int qscale)
void ff_h263_dct_unquantize_intra_rvv(const MPVContext *s, int16_t *block, ptrdiff_t len, int qscale, int aic)
The exact code depends on how similar the blocks are and how related they are to the block
static void dct_unquantize_h263_intra_rvv(const MPVContext *s, int16_t *block, int n, int qscale)