From: Florian Krohm <florian@eich-krohm.de>
Date: Sun, 22 Apr 2012 02:58:49 +0000 (+0000)
Subject: Update s390 status
X-Git-Tag: svn/VALGRIND_3_8_0~335
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=cfa7e16ebcd7a0546dac396d970b12b1deac9169;p=thirdparty%2Fvalgrind.git

Update s390 status


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12533
---

diff --git a/docs/internals/t-chaining-notes.txt b/docs/internals/t-chaining-notes.txt
index 537470d12d..5ed7cbaf75 100644
--- a/docs/internals/t-chaining-notes.txt
+++ b/docs/internals/t-chaining-notes.txt
@@ -2,7 +2,7 @@
 Verification todo
 ~~~~~~~~~~~~~~~~~
 check that illegal insns on all targets don't cause the _toIR.c's to
-assert.  [DONE: amd64 x86 ppc32 ppc64 arm s390??]
+assert.  [DONE: amd64 x86 ppc32 ppc64 arm s390]
 
 check also with --vex-guest-chase-cond=yes
 
@@ -30,6 +30,7 @@ ditto ARM, Ld8S
 
 all backends: iselStmt(Ist_Exit) vs iselNext: make sure that the same
 JKs are handled, else it's not safe against branch sense switching
+[DONE: s390]
 
 Comments that used to be in m_scheduler.c:
    tchaining tests: