| 2baf7530db4074d01a1a0fc8673c975bf2b50787 |
|
26-Jul-2012 |
florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> |
Due to s390's dealings with invalid insns we need to do two things
- advance the guest_IA to the next insn after raising the signal
- adjusting the address in a complaint to point to the failing insn
(after guest_IA has been advanced)
Update testcases .exp files.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12787 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/s390x/op_exception.stderr.exp
|
| 1a22a57936df184cba5e86316b0ebe0d789a5923 |
|
23-Jul-2012 |
florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> |
Update expected results.
This is the companion patch to VEX r2444 which backs out the special
handling for the 00 opcode.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12776 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/s390x/op_exception.stderr.exp
|
| 84c90e6090c570249f8a81911c6e5622d4a4fa04 |
|
09-Aug-2011 |
florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> |
Followup to VEX r2189 -- handling invalid opcode 00 specially.
Update golden log for testcase op_exception which no longer
complains about invalid opcode 00.
Add testcase op00.c
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11958 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/s390x/op_exception.stderr.exp
|
| 852c640f09bde263e91eefb9ef35af1e88466a95 |
|
13-Apr-2011 |
sewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9> |
Test cases for #270082 (s390x: Make sure to point the PSW address to
the next address on SIGILL)
(Christian Borntraeger <borntraeger@de.ibm.com>)
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11694 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/none/tests/s390x/op_exception.stderr.exp
|