From f359d716eaa2661f7daa5831cf3fe648726a4dca Mon Sep 17 00:00:00 2001 From: Edjunior Barbosa Machado Date: Wed, 28 Nov 2012 20:07:19 +0000 Subject: [PATCH] 2012-11-28 Edjunior Machado * rs6000-tdep.c (gdb_print_insn_powerpc): Remove info->mach checking, since now it is being done by binutils' powerpc_init_dialect(). --- gdb/ChangeLog | 5 +++++ gdb/rs6000-tdep.c | 15 --------------- 2 files changed, 5 insertions(+), 15 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 632f6cf99fb..1eb4c8f8dc3 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2012-11-28 Edjunior Machado + + * rs6000-tdep.c (gdb_print_insn_powerpc): Remove info->mach checking, + since now it is being done by binutils' powerpc_init_dialect(). + 2012-11-28 Tom Tromey PR gdb/14290: diff --git a/gdb/rs6000-tdep.c b/gdb/rs6000-tdep.c index 1797cc524b5..07b81bce685 100644 --- a/gdb/rs6000-tdep.c +++ b/gdb/rs6000-tdep.c @@ -3084,21 +3084,6 @@ find_variant_by_arch (enum bfd_architecture arch, unsigned long mach) static int gdb_print_insn_powerpc (bfd_vma memaddr, disassemble_info *info) { - if (!info->disassembler_options) - { - /* When debugging E500 binaries and disassembling code containing - E500-specific (SPE) instructions, one sometimes sees AltiVec - instructions instead. The opcode spaces for SPE instructions - and AltiVec instructions overlap, and specifiying the "any" cpu - looks for AltiVec instructions first. If we know we're - debugging an E500 binary, however, we can specify the "e500x2" - cpu and get much more sane disassembly output. */ - if (info->mach == bfd_mach_ppc_e500) - info->disassembler_options = "e500x2"; - else - info->disassembler_options = "any"; - } - if (info->endian == BFD_ENDIAN_BIG) return print_insn_big_powerpc (memaddr, info); else -- 2.30.2