Macros | Functions
v210dec_init.h File Reference
#include <stdint.h>
#include "config.h"
#include "libavutil/attributes.h"
#include "libavutil/bswap.h"
#include "v210dec.h"

Go to the source code of this file.


#define READ_PIXELS(a, b, c)


static void v210_planar_unpack_c (const uint32_t *src, uint16_t *y, uint16_t *u, uint16_t *v, int width)
static av_unused av_cold void ff_v210dec_init (V210DecContext *s)

Macro Definition Documentation


#define READ_PIXELS (   a,
do { \
val = av_le2ne32(*src++); \
*a++ = val & 0x3FF; \
*b++ = (val >> 10) & 0x3FF; \
*c++ = (val >> 20) & 0x3FF; \
} while (0)

Definition at line 34 of file v210dec_init.h.

Function Documentation

◆ v210_planar_unpack_c()

static void v210_planar_unpack_c ( const uint32_t *  src,
uint16_t *  y,
uint16_t *  u,
uint16_t *  v,
int  width 

Definition at line 42 of file v210dec_init.h.

Referenced by ff_v210dec_init().

◆ ff_v210dec_init()

static av_unused av_cold void ff_v210dec_init ( V210DecContext s)

Definition at line 54 of file v210dec_init.h.

Referenced by checkasm_check_v210dec(), decode_frame(), and decode_init().

#define b
Definition: input.c:41
static double val(void *priv, double ch)
Definition: aeval.c:78
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
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:41
#define av_le2ne32(x)
Definition: bswap.h:92
INIT_CLIP pixel * src
Definition: h264pred_template.c:418