FFmpeg

Commit Graph

Author	SHA1	Message	Date
Janne Grunau	f0f54117c8	checkasm: x86: post commit review fixes Check the full FPU tag word instead of only the lower half and simplify the comparison. Use upper-case function base name as macro name to instantiate both checked_call variants.	9 years ago
Janne Grunau	711781d7a1	x86: checkasm: check for or handle missing cleanup after MMX instructions Not every asm routine is expected clear the MMX state after returning. It is however a requisite for testing floating point code in checkasm. Annotate functions requiring cleanup with declare_func_emms() and issue emms after the call. The remaining functions are checked for having a cleared MMX state after return.	9 years ago
Henrik Gramner	cc28552100	checkasm/x86: Correctly handle variadic functions The System V ABI on x86-64 specifies that the al register contains an upper bound of the number of arguments passed in vector registers when calling variadic functions, so we aren't allowed to clobber it. checkasm_fail_func() is a variadic function so also zero al before calling it. Signed-off-by: Anton Khirnov <anton@khirnov.net>	9 years ago
Henrik Gramner	7ca1de5b4f	checkasm/x86: Correctly handle variadic functions The System V ABI on x86-64 specifies that the al register contains an upper bound of the number of arguments passed in vector registers when calling variadic functions, so we aren't allowed to clobber it. checkasm_fail_func() is a variadic function so also zero al before calling it.	9 years ago
Henrik Gramner	c457bdebe7	checkasm: Fix floating point arguments on 64-bit Windows Signed-off-by: Anton Khirnov <anton@khirnov.net>	9 years ago
Henrik Gramner	33a58d7bf4	checkasm: Fix floating point arguments on 64-bit Windows	9 years ago
Henrik Gramner	515b69f8f8	checkasm: Explicitly declare function prototypes Now we no longer have to rely on function pointers intentionally declared without specified argument types. This makes it easier to support functions with floating point parameters or return values as well as functions returning 64-bit values on 32-bit architectures. It also avoids having to explicitly cast strides to ptrdiff_t for example. Signed-off-by: Anton Khirnov <anton@khirnov.net>	9 years ago
Henrik Gramner	e13da244f4	checkasm: x86: properly save rdx/edx in checked_call() If the return value doesn't fit in a single register rdx/edx can in some cases be used in addition to rax/eax. Doesn't affect any of the existing checkasm tests but might be useful later. Also comment the relevant code a bit better. Signed-off-by: Anton Khirnov <anton@khirnov.net>	9 years ago
Henrik Gramner	e6b8797b82	checkasm: x86: properly save rdx/edx in checked_call() If the return value doesn't fit in a single register rdx/edx can in some cases be used in addition to rax/eax. Doesn't affect any of the existing checkasm tests but might be useful later. Also comment the relevant code a bit better.	9 years ago
Henrik Gramner	18b101ff59	checkasm: Explicitly declare function prototypes Now we no longer have to rely on function pointers intentionally declared without specified argument types. This makes it easier to support functions with floating point parameters or return values as well as functions returning 64-bit values on 32-bit architectures. It also avoids having to explicitly cast strides to ptrdiff_t for example.	9 years ago
Henrik Gramner	8bc67ec2c0	Checkasm: assembly testing and benchmarking tool It provides the following features: * verify correctness by comparing output to the C version. * detect failure to save and restore clobbered callee-saved registers. * detect 32-bit parameters being used as if they were 64-bit in x86-64 (the upper halves are not guaranteed to be zero - but in practice they very often are, which makes those bugs hard to spot otherwise). * easy benchmarking. Compile by running 'make checkasm'. Execute by running 'tests/checkasm/checkasm'. Optional arguments are '--bench' to run benchmarks for all functions, '--bench=<pattern>' to run benchmarks for all functions that starts with <pattern>, and '<integer>' to seed the PRNG for reproducible results. Contains unit tests for most h264pred functions to get started, more tests can be added afterwards using those as a reference. Loosely based on code from x264. Currently only supports x86 and x86-64, but additional architectures shouldn't be too much of an obstacle to add. Note that functions with floating point parameters or floating point return values are not supported. Some compiler-specific features or preprocessor hacks would likely be required to add support for that. Signed-off-by: Janne Grunau <janne-libav@jannau.net>	9 years ago

14 Commits (d3662777e070b297ead7c23883d1a7e77d37193f)