2012-11-28 Edjunior Machado <emachado@linux.vnet.ibm.com>
authorEdjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Wed, 28 Nov 2012 20:07:19 +0000 (20:07 +0000)
committerEdjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Wed, 28 Nov 2012 20:07:19 +0000 (20:07 +0000)
* rs6000-tdep.c (gdb_print_insn_powerpc): Remove info->mach checking,
since now it is being done by binutils' powerpc_init_dialect().

gdb/ChangeLog
gdb/rs6000-tdep.c

index 632f6cf99fbac4eaa07230e3f21205285ffc9b97..1eb4c8f8dc32bc8447a4818c48e89e919ddcc1a8 100644 (file)
@@ -1,3 +1,8 @@
+2012-11-28  Edjunior Machado  <emachado@linux.vnet.ibm.com>
+
+       * 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  <tromey@redhat.com>
 
        PR gdb/14290:
index 1797cc524b5debf751c5c4137e6de925e5757501..07b81bce685bb24aa1b09d2357972544b17149a8 100644 (file)
@@ -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
This page took 0.033525 seconds and 4 git commands to generate.