Go to the documentation of this file.
29 #define FUNC(n) AV_JOIN(n ## _, SAMPLE_SIZE)
32 # define sum_type int64_t
33 # define MUL(a, b) MUL64(a, b)
34 # define CLIP(x) av_clipl_int32(x)
36 # define sum_type int32_t
37 # define MUL(a, b) ((a) * (b))
42 int c = coefs[(x)-1]; \
53 for (
i = order;
i <
len;
i += 2) {
112 for (
i = 0;
i < order;
i++)
115 for (
i = order;
i <
len;
i += 2) {
119 for (j = 0; j < order; j++) {
static av_always_inline void FUNC() lpc_encode_unrolled(int32_t *res, const int32_t *smp, int len, int order, const int32_t *coefs, int shift, int big)
static void FUNC() flac_lpc_encode_c(int32_t *res, const int32_t *smp, int len, int order, const int32_t *coefs, int shift)
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 i(width, name, range_min, range_max)
static int shift(int a, int b)