From f17ecb4baca990b57cc57e8337c4e03ecee02742 Mon Sep 17 00:00:00 2001 From: "Maciej W. Rozycki" Date: Fri, 9 Dec 2016 22:50:07 +0000 Subject: MIPS16/opcodes: Use hexadecimal interpretation for the `e' operand code Make the `e' operand code used with raw EXTEND instructions use the hexadecimal rather than decimal format, for consistency with what is actually produced by code in `print_insn_mips16' dedicated to EXTEND disassembly. Due to that special handling the operand code is only interpreted for assembly however, which accepts either format either way, so there is no functional change here. opcodes/ * mips16-opc.c (decode_mips16_operand) <'e'>: Use HINT rather than UINT. gas/ * testsuite/gas/mips/mips16-extend.d: New test. * testsuite/gas/mips/mips16-extend.s: New test source. * testsuite/gas/mips/mips.exp: Run the new test. --- opcodes/ChangeLog | 5 +++++ opcodes/mips16-opc.c | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) (limited to 'opcodes') diff --git a/opcodes/ChangeLog b/opcodes/ChangeLog index 0d0e186..8017b0f 100644 --- a/opcodes/ChangeLog +++ b/opcodes/ChangeLog @@ -1,5 +1,10 @@ 2016-12-09 Maciej W. Rozycki + * mips16-opc.c (decode_mips16_operand) <'e'>: Use HINT rather + than UINT. + +2016-12-09 Maciej W. Rozycki + * mips-dis.c (print_insn_mips16): Use a tab rather than a space to separate `extend' and its uninterpreted argument output. Separate hexadecimal halves of undecoded extended instructions diff --git a/opcodes/mips16-opc.c b/opcodes/mips16-opc.c index 9337e5d..2b0e942 100644 --- a/opcodes/mips16-opc.c +++ b/opcodes/mips16-opc.c @@ -61,7 +61,7 @@ decode_mips16_operand (char type, bfd_boolean extended_p) case 'Z': MAPPED_REG (3, 0, GP, reg_m16_map); case 'a': JUMP (26, 0, 2); - case 'e': UINT (11, 0); + case 'e': HINT (11, 0); case 'i': JALX (26, 0, 2); case 'l': SPECIAL (6, 5, ENTRY_EXIT_LIST); case 'm': SPECIAL (7, 0, SAVE_RESTORE_LIST); -- cgit v1.1