- 13 Apr, 2016 1 commit
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 12 Apr, 2016 2 commits
-
-
Michael Niedermayer authored
Suggested & Approved by: BBB Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
Ronald S. Bultje authored
-
- 22 Feb, 2016 1 commit
-
-
James Almer authored
Also bench a smaller buffer. This drastically reduces --bench runtime and reports smaller, more readable numbers. Reviewed-by:
Michael Niedermayer <michael@niedermayer.cc> Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 19 Feb, 2016 1 commit
-
-
James Almer authored
They will now compile if avcodec is disabled Reviewed-by:
Paul B Mahol <onemda@gmail.com> Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 18 Feb, 2016 1 commit
-
-
Diego Biurrun authored
-
- 14 Feb, 2016 2 commits
-
-
Timothy Gu authored
The test is already slow.
-
Timothy Gu authored
-
- 31 Jan, 2016 3 commits
-
-
Timothy Gu authored
-
foo86 authored
-
foo86 authored
Remove all files and functions which are not going to be reused, and disable all functions and FATE tests temporarily which will be.
-
- 23 Jan, 2016 1 commit
-
-
Geza Lore authored
Some debuggers/profilers use this metadata to determine which function a given instruction is in; without it they get can confused by local labels (if you haven't stripped those). On the other hand, some tools are still confused even with this metadata. e.g. this fixes `gdb`, but not `perf`. Currently only implemented for ELF. Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
- 21 Jan, 2016 2 commits
-
-
Geza Lore authored
Some debuggers/profilers use this metadata to determine which function a given instruction is in; without it they get can confused by local labels (if you haven't stripped those). On the other hand, some tools are still confused even with this metadata. e.g. this fixes `gdb`, but not `perf`. Currently only implemented for ELF.
-
Ronald S. Bultje authored
-
- 07 Jan, 2016 2 commits
-
-
Martin Storsjö authored
This is disabled on iOS, since iOS uses a slightly different ABI for vararg parameters. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Use two separate functions, depending on whether VFP/NEON is available. This is set to require armv5te - it uses blx, which is only available since armv5t, but we don't have a separate configure item for that. (It also uses ldrd, which requires armv5te, but this could be avoided if necessary.) Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 29 Dec, 2015 1 commit
-
-
Janne Grunau authored
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.
-
- 24 Dec, 2015 1 commit
-
-
Alexandra Hájková authored
They were superseded with their integer equivalents. Rename integer decode_hf to decode_hf.
-
- 21 Dec, 2015 5 commits
-
-
Janne Grunau authored
-
Janne Grunau authored
-
Janne Grunau authored
-
Janne Grunau authored
-
Janne Grunau authored
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.
-
- 14 Dec, 2015 1 commit
-
-
Janne Grunau authored
The vector mode was deprecated in ARMv7-A/VFPv3 and various cpu implementations do not support it in hardware. Vector mode code will depending the OS either be emulated in software or result in an illegal instruction on cpus which does not support it. This was not really problem in practice since NEON implementations of the same functions are preferred. It will however become a problem for checkasm which tests every cpu flag separately. Since this is a cpu feature newer cpu do not support anymore the behaviour of this flag differs from the other flags. It can be only activated by runtime cpu feature selection.
-
- 05 Dec, 2015 1 commit
-
-
Anton Khirnov authored
-
- 08 Nov, 2015 1 commit
-
-
Timothy Gu authored
-
- 28 Oct, 2015 1 commit
-
-
Rodger Combs authored
-
- 13 Oct, 2015 1 commit
-
-
Ronald S. Bultje authored
These aren't quite as helpful as the ones in 8bpp, since over there, we can use pmulhrsw, but here the coefficients have too many bits to be able to take advantage of pmulhrsw. However, we can still skip cols for which all coefs are 0, and instead just zero the input data for the row itx. This helps a few % on overall decoding speed.
-
- 06 Oct, 2015 1 commit
-
-
James Almer authored
Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 04 Oct, 2015 1 commit
-
-
Henrik Gramner authored
-
- 03 Oct, 2015 2 commits
-
-
Henrik Gramner authored
-
Henrik Gramner authored
The previous implementation was behaving incorrectly in some corner cases. Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
- 28 Sep, 2015 5 commits
-
-
Henrik Gramner authored
-
Ronald S. Bultje authored
-
Henrik Gramner authored
The previous implementation was behaving incorrectly in some corner cases.
-
Henrik Gramner authored
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>
-
Henrik Gramner authored
Tested functions are internally kept in a binary search tree for efficient lookups. The downside of the current implementation is that the tree quickly becomes unbalanced which causes an unneccessary amount of comparisons between nodes. Improve this by changing the tree into a self-balancing left-leaning red-black tree with a worst case lookup/insertion time complexity of O(log n). Significantly reduces the recursion depth and makes the tests run around 10% faster overall. The relative performance improvement compared to the existing non-balanced tree will also most likely increase as more tests are added. Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
- 27 Sep, 2015 1 commit
-
-
Henrik Gramner authored
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.
-
- 26 Sep, 2015 2 commits
-
-
James Almer authored
Reviewed-by:
Henrik Gramner <henrik@gramner.com> Signed-off-by:
James Almer <jamrial@gmail.com>
-
James Almer authored
Reviewed-by:
Henrik Gramner <henrik@gramner.com> Signed-off-by:
James Almer <jamrial@gmail.com>
-