Go to the documentation of this file.
22 #ifndef AVCODEC_AAC_AACDEC_AC_H
23 #define AVCODEC_AAC_AACDEC_AC_H
40 #define FF_AAC_AC_ESCAPE 16
50 const uint16_t *cdf, uint16_t cdf_len);
void ff_aac_ac_init(AACArith *ac, GetBitContext *gb)
uint32_t ff_aac_ac_get_context(AACArithState *state, uint32_t old_c, int idx, int len)
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
The reader does not expect b to be semantically here and if the code is changed by maybe adding a a division or other the signedness will almost certainly be mistaken To avoid this confusion a new type was SUINT is the C unsigned type but it holds a signed int to use the same example SUINT a
it s the only field you need to keep assuming you have a context There is some magic you don t need to care about around this just let it vf offset
void ff_aac_ac_finish(AACArithState *state, int offset, int nb)
void ff_aac_ac_update_context(AACArithState *state, int idx, uint16_t a, uint16_t b)
uint32_t ff_aac_ac_map_process(AACArithState *state, int reset, int len)
uint16_t ff_aac_ac_decode(AACArith *ac, GetBitContext *gb, const uint16_t *cdf, uint16_t cdf_len)
uint32_t ff_aac_ac_get_pk(uint32_t c)