OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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().
This commit is contained in:
Edjunior Barbosa Machado 2012-11-28 20:07:19 +00:00
parent 0cd61f4402
commit f359d716ea
2 changed files with 5 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/ChangeLog
View 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> 2012-11-28 Tom Tromey <tromey@redhat.com>
PR gdb/14290: PR gdb/14290:

15
gdb/rs6000-tdep.c
View File

@ -3084,21 +3084,6 @@ find_variant_by_arch (enum bfd_architecture arch, unsigned long mach)
static int static int
gdb_print_insn_powerpc (bfd_vma memaddr, disassemble_info *info) 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) if (info->endian == BFD_ENDIAN_BIG)
return print_insn_big_powerpc (memaddr, info); return print_insn_big_powerpc (memaddr, info);
else else