History log of /external/valgrind/memcheck/tests/vbit-test/valgrind.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
5aa9d1ed1857d401087cf55b4c68ab6eb3ffbc56 22-Sep-2015 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add copyright/license comment.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15672 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/vbit-test/valgrind.c
3a142cfb6cc99c48ed821f6ac6490b1667b73e2f 09-Feb-2013 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> s390: Add testcase for these DFP insns: CDGTRA, CXGTR, CGXTR, and CGDTR (VEX r2680).
Update vbit tester. Patch by Maran Pakkirisamy (maranp@linux.vnet.ibm.com).
Part of fixing BZ #307113.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13285 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/vbit-test/valgrind.c
24c9e7f8a22971d9eb0987539ca3a4269b805e1a 16-Nov-2012 carll <carll@a5019735-40e9-0310-863c-91ae7b9d1cf9> vbit-tester, add counts for the number of 1, 2, 3 and 4 operand tests.

This patch adds code to count the number of each type of test. The
number of 1, 2, 3 and 4 operand tests that are generated by the vbit-tester
are counted and printed by the vbit-tester. The user should refer to the
Valgrind output to see if any of the tests failed.

The existing two verbose levels was increased by one level and the the
new output giving the number of tests was inserted as the first verbose
level. The verbose levels are now:

-v shows the number of 1, 2, 3 and 4 operand tests that are generated
-v -v shows IROps being tested
-v -v -v extreme edition, shows input values

This patch is for bugzilla 309229

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13124 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/vbit-test/valgrind.c
f74f5426e8f96ccba3b39994fb596603bf0421e1 13-Sep-2012 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Adjust the vbit tester to deal with shift operations that require
an immediate constant as the shift amount. This is needed for
powerpc Iop_ShlD64 etc. What it basically means that we do not
iterate over the bits in the 2nd operand because there are no
V-bits to set. An immediate constant is always completely defined.
Fixes bugzilla #305948.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12969 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/vbit-test/valgrind.c
bb913cd4cc1e56d7d7798a8b754361a05d01f916 28-Aug-2012 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Add a tester for V-bit propagation through IROps.
The tester is located in memcheck/tests/vbit-test.
It needs the following support on the valgrind / VEX side:
(1) a new client request VG_USERREQ__VEX_INIT_FOR_IRI
(2) a new "special instruction" on all architectures inserted via
VALGRIND_VEX_INJECT_IR
(3) VEX changes to detect the special insn and insert IR (ir_inject.c)

The README file in vbit-test has some more information.
See also VEX r2490. Fixes bugzilla #300102.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12906 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/memcheck/tests/vbit-test/valgrind.c