|
From: <sv...@va...> - 2011-08-08 23:52:13
|
Author: florian
Date: 2011-08-09 00:47:23 +0100 (Tue, 09 Aug 2011)
New Revision: 11958
Log:
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
Added:
trunk/none/tests/s390x/op00.c
trunk/none/tests/s390x/op00.stderr.exp
trunk/none/tests/s390x/op00.vgtest
Modified:
trunk/none/tests/s390x/Makefile.am
trunk/none/tests/s390x/op_exception.stderr.exp
Modified: trunk/none/tests/s390x/Makefile.am
===================================================================
--- trunk/none/tests/s390x/Makefile.am 2011-08-08 02:27:20 UTC (rev 11957)
+++ trunk/none/tests/s390x/Makefile.am 2011-08-08 23:47:23 UTC (rev 11958)
@@ -5,7 +5,7 @@
INSN_TESTS = clc clcle cvb cvd icm lpr tcxb lam_stam xc mvst add sub mul \
and or xor insert div srst fold_And16 flogr sub_EI add_EI \
and_EI or_EI xor_EI insert_EI mul_GE add_GE condloadstore \
- op_exception fgx stck stckf stcke stfle
+ op_exception fgx stck stckf stcke stfle op00
check_PROGRAMS = $(INSN_TESTS) \
ex_sig \
Added: trunk/none/tests/s390x/op00.c
===================================================================
--- trunk/none/tests/s390x/op00.c (rev 0)
+++ trunk/none/tests/s390x/op00.c 2011-08-08 23:47:23 UTC (rev 11958)
@@ -0,0 +1,7 @@
+/* Test for invalid instruction 00. */
+int main(int argc, char *argv[])
+{
+ asm volatile (".hword 0\n");
+ return 0;
+}
+
Added: trunk/none/tests/s390x/op00.stderr.exp
===================================================================
--- trunk/none/tests/s390x/op00.stderr.exp (rev 0)
+++ trunk/none/tests/s390x/op00.stderr.exp 2011-08-08 23:47:23 UTC (rev 11958)
@@ -0,0 +1,5 @@
+
+
+Process terminating with default action of signal 4 (SIGILL)
+ at 0x........: main (op00.c:5)
+
Added: trunk/none/tests/s390x/op00.vgtest
===================================================================
--- trunk/none/tests/s390x/op00.vgtest (rev 0)
+++ trunk/none/tests/s390x/op00.vgtest 2011-08-08 23:47:23 UTC (rev 11958)
@@ -0,0 +1 @@
+prog: op00
Modified: trunk/none/tests/s390x/op_exception.stderr.exp
===================================================================
--- trunk/none/tests/s390x/op_exception.stderr.exp 2011-08-08 02:27:20 UTC (rev 11957)
+++ trunk/none/tests/s390x/op_exception.stderr.exp 2011-08-08 23:47:23 UTC (rev 11958)
@@ -1,30 +1,4 @@
-vex s390->IR: unknown insn: 0000
-valgrind: Unrecognised instruction at address 0x.........
- at 0x........: main (op_exception.c:23)
-Your program just tried to execute an instruction that Valgrind
-did not recognise. There are two possible reasons for this.
-1. Your program has a bug and erroneously jumped to a non-code
- location. If you are running Memcheck and you just saw a
- warning about a bad jump, it's probably your program's fault.
-2. The instruction is legitimate but Valgrind doesn't handle it,
- i.e. it's Valgrind's fault. If you think this is the case or
- you are not sure, please let us know and we'll try to fix it.
-Either way, Valgrind will now raise a SIGILL signal which will
-probably kill your program.
-vex s390->IR: unknown insn: 0000
-valgrind: Unrecognised instruction at address 0x.........
- at 0x........: main (op_exception.c:27)
-Your program just tried to execute an instruction that Valgrind
-did not recognise. There are two possible reasons for this.
-1. Your program has a bug and erroneously jumped to a non-code
- location. If you are running Memcheck and you just saw a
- warning about a bad jump, it's probably your program's fault.
-2. The instruction is legitimate but Valgrind doesn't handle it,
- i.e. it's Valgrind's fault. If you think this is the case or
- you are not sure, please let us know and we'll try to fix it.
-Either way, Valgrind will now raise a SIGILL signal which will
-probably kill your program.
vex s390->IR: unknown insn: FFFF FFFF FFFF
valgrind: Unrecognised instruction at address 0x.........
at 0x........: main (op_exception.c:30)
@@ -38,17 +12,4 @@
you are not sure, please let us know and we'll try to fix it.
Either way, Valgrind will now raise a SIGILL signal which will
probably kill your program.
-vex s390->IR: unknown insn: 0000
-valgrind: Unrecognised instruction at address 0x.........
- at 0x........: main (op_exception.c:34)
-Your program just tried to execute an instruction that Valgrind
-did not recognise. There are two possible reasons for this.
-1. Your program has a bug and erroneously jumped to a non-code
- location. If you are running Memcheck and you just saw a
- warning about a bad jump, it's probably your program's fault.
-2. The instruction is legitimate but Valgrind doesn't handle it,
- i.e. it's Valgrind's fault. If you think this is the case or
- you are not sure, please let us know and we'll try to fix it.
-Either way, Valgrind will now raise a SIGILL signal which will
-probably kill your program.
|