MIPS16/opcodes: Use hexadecimal interpretation for the `e' operand code
authorMaciej W. Rozycki <macro@imgtec.com>
Fri, 9 Dec 2016 22:50:07 +0000 (22:50 +0000)
committerMaciej W. Rozycki <macro@imgtec.com>
Fri, 9 Dec 2016 23:19:52 +0000 (23:19 +0000)
commitf17ecb4baca990b57cc57e8337c4e03ecee02742
tree994ed30c092ff3164f0d1d0157b9d17e0d8cb3c3
parent55af478400524cba7994e353fd9a98ef1543df2f
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.
gas/ChangeLog
gas/testsuite/gas/mips/mips.exp
gas/testsuite/gas/mips/mips16-extend.d [new file with mode: 0644]
gas/testsuite/gas/mips/mips16-extend.s [new file with mode: 0644]
opcodes/ChangeLog
opcodes/mips16-opc.c