The hppa disassembly is different from the others due to leading with
the raw opcode data. This confuses plugins looking for instruction
prefixes to match instructions. For plugins like execlog there is
another mechanism for getting the instruction byte data.
For the sake of consistently just present the instruction assembly
code.
Signed-off-by: Alex Bennée <alex.ben...@linaro.org>
---
disas/hppa.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/disas/hppa.c b/disas/hppa.c
index 22dce9b41bb..dd34cce211b 100644
--- a/disas/hppa.c
+++ b/disas/hppa.c
@@ -1972,10 +1972,6 @@ print_insn_hppa (bfd_vma memaddr, disassemble_info *info)
insn = bfd_getb32 (buffer);
- info->fprintf_func(info->stream, " %02x %02x %02x %02x ",
- (insn >> 24) & 0xff, (insn >> 16) & 0xff,
- (insn >> 8) & 0xff, insn & 0xff);
-
for (i = 0; i < NUMOPCODES; ++i)
{
const struct pa_opcode *opcode = &pa_opcodes[i];
--
2.39.2
