This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
[binutils-gdb] MIPS16/opcodes: Use hexadecimal interpretation for the `e' operand code
- From: sergiodj+buildbot at sergiodj dot net
- To: gdb-testers at sourceware dot org
- Date: Fri, 09 Dec 2016 19:22:11 -0500
- Subject: [binutils-gdb] MIPS16/opcodes: Use hexadecimal interpretation for the `e' operand code
- Authentication-results: sourceware.org; auth=none
*** TEST RESULTS FOR COMMIT f17ecb4baca990b57cc57e8337c4e03ecee02742 ***
Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: f17ecb4baca990b57cc57e8337c4e03ecee02742
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.