Macros | Functions
vp9_mc_template.c File Reference

Go to the source code of this file.


#define ROUNDED_DIV_MVx2(a, b)   (VP56mv) { .x = ROUNDED_DIV(a.x + b.x, 2), .y = ROUNDED_DIV(a.y + b.y, 2) }
#define ROUNDED_DIV_MVx4(a, b, c, d)


static void FN() inter_pred (VP9TileData *td)

Macro Definition Documentation

#define ROUNDED_DIV_MVx2 (   a,
)    (VP56mv) { .x = ROUNDED_DIV(a.x + b.x, 2), .y = ROUNDED_DIV(a.y + b.y, 2) }

Definition at line 24 of file vp9_mc_template.c.

Referenced by inter_pred().

#define ROUNDED_DIV_MVx4 (   a,
(VP56mv) { .x = ROUNDED_DIV(a.x + b.x + c.x + d.x, 4), \
.y = ROUNDED_DIV(a.y + b.y + c.y + d.y, 4) }
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
Definition: undefined.txt:36
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
Definition: undefined.txt:32
#define ROUNDED_DIV(a, b)
Definition: common.h:56
#define b
Definition: input.c:41
Definition: vp56.h:68

Definition at line 26 of file vp9_mc_template.c.

Referenced by inter_pred().

Function Documentation

static void FN() inter_pred ( VP9TileData td)

Definition at line 30 of file vp9_mc_template.c.