Go to the documentation of this file.
28 for (
int i = 0;
i <
len;
i += 8) {
31 for (
int j = 0; j < 8; j++)
33 for (
int j = 0; j < 8; j++)
void ff_audiodsp_init_x86(AudioDSPContext *c)
av_cold void ff_audiodsp_init(AudioDSPContext *c)
av_cold void ff_audiodsp_init_ppc(AudioDSPContext *c)
static void vector_clipf_c(float *dst, const float *src, int len, float min, float max)
av_cold void ff_audiodsp_init_arm(AudioDSPContext *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
static void vector_clip_int32_c(int32_t *dst, const int32_t *src, int32_t min, int32_t max, unsigned int len)
#define i(width, name, range_min, range_max)
static int32_t scalarproduct_int16_c(const int16_t *v1, const int16_t *v2, int order)
void ff_audiodsp_init_riscv(AudioDSPContext *c)