FFmpeg
Macros | Functions
h264dsp.c File Reference

H.264 / AVC / MPEG-4 part10 DSP functions. More...

#include <stdint.h>
#include "libavutil/attributes.h"
#include "libavutil/avassert.h"
#include "avcodec.h"
#include "h264dsp.h"
#include "h264idct.h"
#include "startcode.h"
#include "libavutil/common.h"
#include "h264dsp_template.c"
#include "h264addpx_template.c"

Go to the source code of this file.

Macros

#define BIT_DEPTH   8
 
#define BIT_DEPTH   9
 
#define BIT_DEPTH   10
 
#define BIT_DEPTH   12
 
#define BIT_DEPTH   14
 
#define BIT_DEPTH   8
 
#define BIT_DEPTH   16
 
#define FUNC(a, depth)   a ## _ ## depth ## _c
 
#define ADDPX_DSP(depth)
 
#define H264_DSP(depth)
 

Functions

av_cold void ff_h264dsp_init (H264DSPContext *c, const int bit_depth, const int chroma_format_idc)
 

Detailed Description

H.264 / AVC / MPEG-4 part10 DSP functions.

Author
Michael Niedermayer micha.nosp@m.elni.nosp@m.@gmx..nosp@m.at

Definition in file h264dsp.c.

Macro Definition Documentation

#define BIT_DEPTH   8

Definition at line 63 of file h264dsp.c.

#define BIT_DEPTH   9

Definition at line 63 of file h264dsp.c.

#define BIT_DEPTH   10

Definition at line 63 of file h264dsp.c.

#define BIT_DEPTH   12

Definition at line 63 of file h264dsp.c.

#define BIT_DEPTH   14

Definition at line 63 of file h264dsp.c.

#define BIT_DEPTH   8

Definition at line 63 of file h264dsp.c.

#define BIT_DEPTH   16

Definition at line 63 of file h264dsp.c.

#define FUNC (   a,
  depth 
)    a ## _ ## depth ## _c
#define ADDPX_DSP (   depth)
Value:
c->h264_add_pixels4_clear = FUNC(ff_h264_add_pixels4, depth);\
c->h264_add_pixels8_clear = FUNC(ff_h264_add_pixels8, depth)
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
static void FUNCC() ff_h264_add_pixels4(uint8_t *_dst, int16_t *_src, int stride)
static void FUNCC() ff_h264_add_pixels8(uint8_t *_dst, int16_t *_src, int stride)
#define FUNC(a, depth)

Referenced by ff_h264dsp_init().

#define H264_DSP (   depth)

Referenced by ff_h264dsp_init().

Function Documentation

av_cold void ff_h264dsp_init ( H264DSPContext c,
const int  bit_depth,
const int  chroma_format_idc 
)