Go to the documentation of this file.
43 static void ict_float(
void *_src0,
void *_src1,
void *_src2,
int csize)
49 for (
i = 0;
i < csize;
i++) {
60 static void ict_int(
void *_src0,
void *_src1,
void *_src2,
int csize)
66 for (
i = 0;
i < csize;
i++) {
70 i2 = *
src0 + (2 * *
src1) + ((
int)((-14942
U * *
src1) + (1 << 15)) >> 16);
77 static void rct_int(
void *_src0,
void *_src1,
void *_src2,
int csize)
82 for (
i = 0;
i < csize;
i++) {
static void ict_float(void *_src0, void *_src1, void *_src2, int csize)
void ff_jpeg2000dsp_init_x86(Jpeg2000DSPContext *c)
static void ict_int(void *_src0, void *_src1, void *_src2, int csize)
av_cold void ff_jpeg2000dsp_init(Jpeg2000DSPContext *c)
static const int i_ict_params[4]
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 Float11 * i2f(int i, Float11 *f)
#define i(width, name, range_min, range_max)
static void rct_int(void *_src0, void *_src1, void *_src2, int csize)
static const float f_ict_params[4]