[Valgrind-developers] [valgrind] s390x: disasm-test: Fix thinko

[Florian K. <fk...@so...>]

https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=1d9cca850c5401784fe389b6792cb23c803d6342

commit 1d9cca850c5401784fe389b6792cb23c803d6342
Author: Florian Krohm <fl...@ei...>
Date:   Mon Mar 10 12:36:21 2025 +0000

    s390x: disasm-test: Fix thinko
    
    Remove verbiage about limited support for opcodes with optional operands.
    Optional operands are of no concern for disassembly. The reason is that
    disassembly sees as its input only a sequence of bytes which have no
    indication as to whether some of its bits were explicitly specified or not.
    We're testing the disassembler here - not the assembler.

Diff:
---
 none/tests/s390x/disasm-test/README | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/none/tests/s390x/disasm-test/README b/none/tests/s390x/disasm-test/README
index 54df05cf98..a771c41c98 100644
--- a/none/tests/s390x/disasm-test/README
+++ b/none/tests/s390x/disasm-test/README
@@ -169,10 +169,6 @@ Status
 Only opcodes with extended mnemonics as identified in Appendix J of the
 Principles of Operation are considered.
 
-There is only partial support for opcodes with optional operands.
-In the sense that the generated testcases will always include the
-optional operand.
-
 
 TODO
 ----