Add testcases for CU21. Update opcode table.
authorflorian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9>
Fri, 20 Jul 2012 00:17:16 +0000 (00:17 +0000)
committerflorian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9>
Fri, 20 Jul 2012 00:17:16 +0000 (00:17 +0000)
commit973523422e8af809e31f8ebe788980e4c5ec84e0
tree4c5ff9cae95750f307e9dcfb5746f8fa2cf6d98b
parent00c7dc1c31231e0cce552c4944d42db889e6c4d0
Add testcases for CU21. Update opcode table.
WRT the memcheck test: the good news is we get all the complaints
we want. The bad news is:
- the line numbers from within do_cu21 are off
- there are 2 complaints when attempting to convert from
  an uninitialised input buffer instead of one. One of them has a
  completely bogus line number.

Possibly due to bad debug info?  Let's see what happens on machines
with more recent GCCs.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12765 a5019735-40e9-0310-863c-91ae7b9d1cf9
15 files changed:
docs/internals/s390-opcodes.csv
memcheck/tests/s390x/Makefile.am
memcheck/tests/s390x/cu21.c [new file with mode: 0644]
memcheck/tests/s390x/cu21.stderr.exp [new file with mode: 0644]
memcheck/tests/s390x/cu21.stdout.exp [new file with mode: 0644]
memcheck/tests/s390x/cu21.vgtest [new file with mode: 0644]
none/tests/s390x/Makefile.am
none/tests/s390x/cu21.c [new file with mode: 0644]
none/tests/s390x/cu21.stderr.exp [new file with mode: 0644]
none/tests/s390x/cu21.stdout.exp [new file with mode: 0644]
none/tests/s390x/cu21.vgtest [new file with mode: 0644]
none/tests/s390x/cu21_1.c [new symlink]
none/tests/s390x/cu21_1.stderr.exp [new file with mode: 0644]
none/tests/s390x/cu21_1.stdout.exp [new file with mode: 0644]
none/tests/s390x/cu21_1.vgtest [new file with mode: 0644]