History log of /external/valgrind/none/tests/x86/smc1.vgtest
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
6c3a219727dead14309abf431f72ca1f99b8ca37 24-Jul-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Rename --smc-support= to --smc-check=.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4237 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/x86/smc1.vgtest
8c30ec2ade2b7f1196760c4db9a8e9fa9a876afe 07-Jul-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> Modify this test so it no longer uses client requests, but instead
relies on --smc-support=all to work correctly. Hence it tests the
s-m-c support at least on x86. Jump through various hoops to defeat
vex's basic-block-chasing optimisation, which has an annoying habit of
making this test work correctly even without --smc-support=all.



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4123 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/x86/smc1.vgtest
937411f6e8e378bd71288e0f6efcf16892e5acb1 06-Jul-2005 sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> smc1 is an x86-specific test; re-home it accordingly. (How did this
one evade detection for so long?)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4119 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/x86/smc1.vgtest