Go to the documentation of this file.
40 for (
i = 0;
i <
len;
i += 8)
41 c->int32_to_float_fmul_scalar(&dst[
i], &
src[
i], *
mul++, 8);
void ff_fmt_convert_init_ppc(FmtConvertContext *c)
static float mul(float src0, float src1)
void ff_fmt_convert_init_mips(FmtConvertContext *c)
void ff_fmt_convert_init_riscv(FmtConvertContext *c)
void ff_fmt_convert_init_x86(FmtConvertContext *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
static void int32_to_float_fmul_scalar_c(float *dst, const int32_t *src, float mul, int len)
static void int32_to_float_fmul_array8_c(FmtConvertContext *c, float *dst, const int32_t *src, const float *mul, int len)
#define i(width, name, range_min, range_max)
av_cold void ff_fmt_convert_init_arm(FmtConvertContext *c)
av_cold void ff_fmt_convert_init(FmtConvertContext *c)
av_cold void ff_fmt_convert_init_aarch64(FmtConvertContext *c)