FFmpeg  4.3
Macros | Functions
rv40dsp_init_arm.c File Reference
#include <stdint.h>
#include "libavutil/attributes.h"
#include "libavcodec/avcodec.h"
#include "libavcodec/rv34dsp.h"
#include "libavutil/arm/cpu.h"

Go to the source code of this file.

Macros

#define DECL_QPEL3(type, w, pos)
 
#define DECL_QPEL2(w, pos)
 
#define DECL_QPEL_XY(x, y)
 
#define DECL_QPEL_Y(y)
 

Functions

 DECL_QPEL_Y (0)
 
 DECL_QPEL_Y (1)
 
 DECL_QPEL_Y (2)
 
 DECL_QPEL_Y (3)
 
void ff_put_rv40_chroma_mc8_neon (uint8_t *, uint8_t *, int, int, int, int)
 
void ff_put_rv40_chroma_mc4_neon (uint8_t *, uint8_t *, int, int, int, int)
 
void ff_avg_rv40_chroma_mc8_neon (uint8_t *, uint8_t *, int, int, int, int)
 
void ff_avg_rv40_chroma_mc4_neon (uint8_t *, uint8_t *, int, int, int, int)
 
void ff_rv40_weight_func_16_neon (uint8_t *, uint8_t *, uint8_t *, int, int, ptrdiff_t)
 
void ff_rv40_weight_func_8_neon (uint8_t *, uint8_t *, uint8_t *, int, int, ptrdiff_t)
 
int ff_rv40_h_loop_filter_strength_neon (uint8_t *src, ptrdiff_t stride, int beta, int beta2, int edge, int *p1, int *q1)
 
int ff_rv40_v_loop_filter_strength_neon (uint8_t *src, ptrdiff_t stride, int beta, int beta2, int edge, int *p1, int *q1)
 
void ff_rv40_h_weak_loop_filter_neon (uint8_t *src, ptrdiff_t stride, int filter_p1, int filter_q1, int alpha, int beta, int lim_p0q0, int lim_q1, int lim_p1)
 
void ff_rv40_v_weak_loop_filter_neon (uint8_t *src, ptrdiff_t stride, int filter_p1, int filter_q1, int alpha, int beta, int lim_p0q0, int lim_q1, int lim_p1)
 
static av_cold void rv40dsp_init_neon (RV34DSPContext *c)
 
av_cold void ff_rv40dsp_init_arm (RV34DSPContext *c)
 

Macro Definition Documentation

◆ DECL_QPEL3

#define DECL_QPEL3 (   type,
  w,
  pos 
)
Value:
void ff_ ## type ## _rv40_qpel ## w ## _mc ## pos ## _neon(uint8_t *dst, \
const uint8_t *src, \
ptrdiff_t stride)

Definition at line 28 of file rv40dsp_init_arm.c.

◆ DECL_QPEL2

#define DECL_QPEL2 (   w,
  pos 
)
Value:
DECL_QPEL3(put, w, pos); \
DECL_QPEL3(avg, w, pos)

Definition at line 33 of file rv40dsp_init_arm.c.

◆ DECL_QPEL_XY

#define DECL_QPEL_XY (   x,
 
)
Value:
DECL_QPEL2(16, x ## y); \
DECL_QPEL2(8, x ## y)

Definition at line 37 of file rv40dsp_init_arm.c.

◆ DECL_QPEL_Y

#define DECL_QPEL_Y (   y)
Value:
DECL_QPEL_XY(0, y); \
DECL_QPEL_XY(1, y); \
DECL_QPEL_XY(2, y); \
DECL_QPEL_XY(3, y); \

Definition at line 41 of file rv40dsp_init_arm.c.

Function Documentation

◆ DECL_QPEL_Y() [1/4]

DECL_QPEL_Y ( )

◆ DECL_QPEL_Y() [2/4]

DECL_QPEL_Y ( )

◆ DECL_QPEL_Y() [3/4]

DECL_QPEL_Y ( )

◆ DECL_QPEL_Y() [4/4]

DECL_QPEL_Y ( )

◆ ff_put_rv40_chroma_mc8_neon()

void ff_put_rv40_chroma_mc8_neon ( uint8_t ,
uint8_t ,
int  ,
int  ,
int  ,
int   
)

Referenced by rv40dsp_init_neon().

◆ ff_put_rv40_chroma_mc4_neon()

void ff_put_rv40_chroma_mc4_neon ( uint8_t ,
uint8_t ,
int  ,
int  ,
int  ,
int   
)

Referenced by rv40dsp_init_neon().

◆ ff_avg_rv40_chroma_mc8_neon()

void ff_avg_rv40_chroma_mc8_neon ( uint8_t ,
uint8_t ,
int  ,
int  ,
int  ,
int   
)

Referenced by rv40dsp_init_neon().

◆ ff_avg_rv40_chroma_mc4_neon()

void ff_avg_rv40_chroma_mc4_neon ( uint8_t ,
uint8_t ,
int  ,
int  ,
int  ,
int   
)

Referenced by rv40dsp_init_neon().

◆ ff_rv40_weight_func_16_neon()

void ff_rv40_weight_func_16_neon ( uint8_t ,
uint8_t ,
uint8_t ,
int  ,
int  ,
ptrdiff_t   
)

Referenced by rv40dsp_init_neon().

◆ ff_rv40_weight_func_8_neon()

void ff_rv40_weight_func_8_neon ( uint8_t ,
uint8_t ,
uint8_t ,
int  ,
int  ,
ptrdiff_t   
)

Referenced by rv40dsp_init_neon().

◆ ff_rv40_h_loop_filter_strength_neon()

int ff_rv40_h_loop_filter_strength_neon ( uint8_t src,
ptrdiff_t  stride,
int  beta,
int  beta2,
int  edge,
int p1,
int q1 
)

Referenced by rv40dsp_init_neon().

◆ ff_rv40_v_loop_filter_strength_neon()

int ff_rv40_v_loop_filter_strength_neon ( uint8_t src,
ptrdiff_t  stride,
int  beta,
int  beta2,
int  edge,
int p1,
int q1 
)

Referenced by rv40dsp_init_neon().

◆ ff_rv40_h_weak_loop_filter_neon()

void ff_rv40_h_weak_loop_filter_neon ( uint8_t src,
ptrdiff_t  stride,
int  filter_p1,
int  filter_q1,
int  alpha,
int  beta,
int  lim_p0q0,
int  lim_q1,
int  lim_p1 
)

Referenced by rv40dsp_init_neon().

◆ ff_rv40_v_weak_loop_filter_neon()

void ff_rv40_v_weak_loop_filter_neon ( uint8_t src,
ptrdiff_t  stride,
int  filter_p1,
int  filter_q1,
int  alpha,
int  beta,
int  lim_p0q0,
int  lim_q1,
int  lim_p1 
)

Referenced by rv40dsp_init_neon().

◆ rv40dsp_init_neon()

static av_cold void rv40dsp_init_neon ( RV34DSPContext c)
static

Definition at line 75 of file rv40dsp_init_arm.c.

Referenced by ff_rv40dsp_init_arm().

◆ ff_rv40dsp_init_arm()

av_cold void ff_rv40dsp_init_arm ( RV34DSPContext c)

Definition at line 144 of file rv40dsp_init_arm.c.

Referenced by ff_rv40dsp_init().

stride
int stride
Definition: mace.c:144
DECL_QPEL2
#define DECL_QPEL2(w, pos)
Definition: rv40dsp_init_arm.c:33
DECL_QPEL3
#define DECL_QPEL3(type, w, pos)
Definition: rv40dsp_init_arm.c:28
x
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable Submitting the results to the FFmpeg result aggregation server ****************************************************************To submit your results to the server you should run fate through the shell script ‘tests fate sh’ from the FFmpeg sources This script needs to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ v’ options You should get detailed output concerning your SSH configuration and the authentication process The only thing left is to automate the execution of the fate sh script and the synchronisation of the samples directory Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo x
Definition: fate.txt:150
type
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 type
Definition: writing_filters.txt:86
DECL_QPEL_XY
#define DECL_QPEL_XY(x, y)
Definition: rv40dsp_init_arm.c:37
src
#define src
Definition: vp8dsp.c:254
avg
#define avg(a, b, c, d)
Definition: colorspacedsp_template.c:28
uint8_t
uint8_t
Definition: audio_convert.c:194
w
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable Submitting the results to the FFmpeg result aggregation server ****************************************************************To submit your results to the server you should run fate through the shell script ‘tests fate sh’ from the FFmpeg sources This script needs to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ v’ options You should get detailed output concerning your SSH configuration and the authentication process The only thing left is to automate the execution of the fate sh script and the synchronisation of the samples directory Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o w
Definition: fate.txt:150
pos
unsigned int pos
Definition: spdifenc.c:410