Go to the documentation of this file.
32 #define randomize_buf(buf, len) \
34 for (int i = 0; i < len; i++) \
40 #define BUF_SIZE 1088 // multiple of 16
55 "scalarproduct_and_madd_int16")) {
60 memcpy(dst0, v1,
sizeof (*dst0) *
BUF_SIZE);
61 memcpy(dst1, v1,
sizeof (*dst1) *
BUF_SIZE);
64 if (memcmp(dst0, dst1,
sizeof (*dst0) *
BUF_SIZE) != 0 ||
ref !=
val)
70 report(
"scalarproduct_and_madd_int16");
75 #define BUF_SIZE 1088 // multiple of 16
90 "scalarproduct_and_madd_int32")) {
95 memcpy(dst0, v1,
sizeof (*dst0) *
BUF_SIZE);
96 memcpy(dst1, v1,
sizeof (*dst1) *
BUF_SIZE);
99 if (memcmp(dst0, dst1,
sizeof (*dst0) *
BUF_SIZE) != 0 ||
ref !=
val)
105 report(
"scalarproduct_and_madd_int32");
#define check_func(func,...)
av_cold void ff_llauddsp_init(LLAudDSPContext *c)
#define randomize_buf(buf, len)
static void check_scalarproduct_and_madd_int32(LLAudDSPContext *c)
static double val(void *priv, double ch)
#define LOCAL_ALIGNED_16(t, v,...)
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
void checkasm_check_llauddsp(void)
static int ref[MAX_W *MAX_W]
static void check_scalarproduct_and_madd_int16(LLAudDSPContext *c)
#define declare_func(ret,...)