Go to the documentation of this file.
22 #ifndef AVCODEC_MATHOPS_H
23 #define AVCODEC_MATHOPS_H
31 #define MAX_NEG_CROP 1024
54 # define MUL64(a,b) ((int64_t)(a) * (int64_t)(b))
58 # define MULL(a,b,s) (MUL64(a, b) >> (s))
69 return ((uint64_t)(
a) * (uint64_t)(
b))>>32;
74 # define MAC64(d, a, b) ((d) += MUL64(a, b))
78 # define MLS64(d, a, b) ((d) -= MUL64(a, b))
83 # define MAC16(rt, ra, rb) rt += (ra) * (rb)
88 # define MUL16(ra, rb) ((ra) * (rb))
92 # define MLS16(rt, ra, rb) ((rt) -= (ra) * (rb))
97 #define mid_pred mid_pred
116 #define median4 median4
133 union {
unsigned u;
int s; } v = { (unsigned)
val <<
shift };
141 return (
val << ((8 *
sizeof(
int)) -
bits)) >> ((8 *
sizeof(
int)) -
bits);
146 #define COPY3_IF_LT(x, y, a, b, c, d)\
155 #define MASK_ABS(mask, level) do { \
156 mask = level >> 31; \
157 level = (level ^ mask) - mask; \
162 # define NEG_SSR32(a,s) ((( int32_t)(a))>>(32-(s)))
166 # define NEG_USR32(a,s) (((uint32_t)(a))>>(32-(s)))
171 # define PACK_2U8(a,b) (((a) << 8) | (b))
174 # define PACK_4U8(a,b,c,d) (((a) << 24) | ((b) << 16) | ((c) << 8) | (d))
177 # define PACK_2U16(a,b) (((a) << 16) | (b))
181 # define PACK_2U8(a,b) (((b) << 8) | (a))
184 # define PACK_4U8(a,b,c,d) (((d) << 24) | ((c) << 16) | ((b) << 8) | (a))
187 # define PACK_2U16(a,b) (((b) << 16) | (a))
192 # define PACK_2S8(a,b) PACK_2U8((a)&255, (b)&255)
195 # define PACK_4S8(a,b,c,d) PACK_4U8((a)&255, (b)&255, (c)&255, (d)&255)
198 # define PACK_2S16(a,b) PACK_2U16((a)&0xffff, (b)&0xffff)
202 # define FASTDIV(a,b) ((uint32_t)((((uint64_t)a) * ff_inverse[b]) >> 32))
206 #define ff_sqrt ff_sqrt
219 unsigned int c =
a >> (
s + 2);
224 return b - (
a <
b *
b);
static av_always_inline uint32_t bitswap_32(uint32_t x)
#define u(width, name, range_min, range_max)
static int8_t ff_u8_to_s8(uint8_t a)
const uint8_t ff_reverse[256]
static av_const unsigned zero_extend(unsigned val, unsigned bits)
const uint32_t ff_inverse[257]
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
static double val(void *priv, double ch)
static av_always_inline unsigned UMULH(unsigned a, unsigned b)
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
const uint8_t ff_sqrt_tab[256]
const uint8_t ff_zigzag_scan[16+1]
const uint8_t ff_crop_tab[256+2 *MAX_NEG_CROP]
static av_always_inline int MULH(int a, int b)
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
static av_const float ff_sqrf(float a)
const uint8_t ff_zigzag_direct[64]
static av_const int sign_extend(int val, unsigned bits)
static int shift(int a, int b)