Go to the documentation of this file.
117 static const uint32_t
pixel_mask[3] = { 0xffffffff, 0x01ff01ff, 0x03ff03ff };
119 #define SIZEOF_PIXEL ((bit_depth + 7) / 8)
120 #define BUF_SIZE (3 * 16 * 17)
122 #define check_pred_func(func, name, mode_name) \
123 (mode_name && ((codec_ids[codec] == AV_CODEC_ID_H264) ? \
124 check_func(func, "pred%s_%s_%d", name, mode_name, bit_depth) : \
125 check_func(func, "pred%s_%s", name, mode_name)))
127 #define randomize_buffers() \
129 uint32_t mask = pixel_mask[bit_depth - 8]; \
131 for (i = 0; i < BUF_SIZE; i += 4) { \
132 uint32_t r = rnd() & mask; \
133 AV_WN32A(buf0 + i, r); \
134 AV_WN32A(buf1 + i, r); \
138 #define src0 (buf0 + 4 * 16)
139 #define src1 (buf1 + 4 * 16)
142 int codec,
int chroma_format,
int bit_depth)
144 if (chroma_format == 1) {
145 uint8_t *topright = buf0 + 2*16;
149 for (pred_mode = 0; pred_mode < 15; pred_mode++) {
163 int codec,
int chroma_format,
int bit_depth)
168 for (pred_mode = 0; pred_mode < 11; pred_mode++) {
169 if (
check_pred_func(
h->pred8x8[pred_mode], (chroma_format == 2) ?
"8x16" :
"8x8",
182 int codec,
int chroma_format,
int bit_depth)
184 if (chroma_format == 1) {
188 for (pred_mode = 0; pred_mode < 9; pred_mode++) {
202 int codec,
int chroma_format,
int bit_depth)
208 for (pred_mode = 0; pred_mode < 12; pred_mode++) {
211 for (neighbors = 0; neighbors <= 0xc000; neighbors += 0x4000) {
212 int has_topleft = neighbors & 0x8000;
213 int has_topright = neighbors & 0x4000;
234 static const struct {
250 for (codec = 0; codec < 4; codec++) {
int(* func)(AVBPrint *dst, const char *in, const char *arg)
#define declare_func_emms(cpu_flags, ret,...)
static void bit_depth(AudioStatsContext *s, uint64_t mask, uint64_t imask, AVRational *depth)
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 default minimum maximum flags name is the option name
static const char *const pred16x16_modes[4][9]
static const char *const pred4x4_modes[4][15]
static const uint32_t pixel_mask[3]
static const char *const pred8x8_modes[4][11]
#define VERT_LEFT_PRED_RV40_NODOWN
static void check_pred8x8(H264PredContext *h, uint8_t *buf0, uint8_t *buf1, int codec, int chroma_format, int bit_depth)
static void check_pred4x4(H264PredContext *h, uint8_t *buf0, uint8_t *buf1, int codec, int chroma_format, int bit_depth)
static const int codec_ids[4]
#define check_pred_func(func, name, mode_name)
void checkasm_check_h264pred(void)
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 X fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg Duo ug o o X fate suite fate suite ffmpeg can be set or it has a meaning only while running the regression tests ‘THREADS’ Specify how many threads to use while running regression tests
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 test
#define DIAG_DOWN_LEFT_PRED_RV40_NODOWN
static void check_pred16x16(H264PredContext *h, uint8_t *buf0, uint8_t *buf1, int codec, int chroma_format, int bit_depth)
static void check_pred8x8l(H264PredContext *h, uint8_t *buf0, uint8_t *buf1, int codec, int chroma_format, int bit_depth)
#define HOR_UP_PRED_RV40_NODOWN
#define ALZHEIMER_DC_L00_PRED8x8
#define randomize_buffers()
#define FF_ARRAY_ELEMS(a)
#define AV_CPU_FLAG_MMX
standard MMX
typedef void(RENAME(mix_any_func_type))
av_cold void ff_h264_pred_init(H264PredContext *h, int codec_id, const int bit_depth, int chroma_format_idc)
Set the intra prediction function pointers.
#define AV_CPU_FLAG_MMXEXT
SSE integer functions or AMD MMX ext.
#define ALZHEIMER_DC_0L0_PRED8x8
Context for storing H.264 prediction functions.
#define ALZHEIMER_DC_L0T_PRED8x8
#define LOCAL_ALIGNED_16(t, v,...)
#define ALZHEIMER_DC_0LT_PRED8x8