Go to the documentation of this file.
36 int dst_index,
const void *
src0,
37 unsigned int index,
int frac);
39 int dst_index,
const void *
src0,
40 unsigned int index,
int frac);
42 int dst_index,
const void *
src0,
43 unsigned int index,
int frac);
45 int dst_index,
const void *
src0,
46 unsigned int index,
int frac);
@ AV_SAMPLE_FMT_FLTP
float, planar
av_cold void ff_audio_resample_init_aarch64(ResampleContext *c, enum AVSampleFormat sample_fmt)
@ AV_SAMPLE_FMT_S32P
signed 32 bits, planar
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
static atomic_int cpu_flags
AV_CHECK_OFFSET(struct ResampleContext, filter_bank, FILTER_BANK)
void ff_resample_one_dbl_neon(struct ResampleContext *c, void *dst0, int dst_index, const void *src0, unsigned int index, int frac)
void ff_resample_one_s32_neon(struct ResampleContext *c, void *dst0, int dst_index, const void *src0, unsigned int index, int frac)
void ff_resample_one_s16_neon(struct ResampleContext *c, void *dst0, int dst_index, const void *src0, unsigned int index, int frac)
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_resample_one_flt_neon(struct ResampleContext *c, void *dst0, int dst_index, const void *src0, unsigned int index, int frac)
@ AV_SAMPLE_FMT_S16P
signed 16 bits, planar
AVSampleFormat
Audio sample formats.
@ AV_SAMPLE_FMT_DBLP
double, planar