Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: bergner@vnet.ibm.com (Peter Bergner)
Cc: palves@redhat.com (Pedro Alves), amodra@gmail.com (Alan Modra),
	       gdb-patches@sourceware.org,
	binutils@sourceware.org (binutils)
Subject: Re: [PATCH, RFC] Add support for choosing disassembler cpu in GDB for POWER.
Date: Fri, 28 Oct 2016 18:47:00 -0000	[thread overview]
Message-ID: <20161028184714.6B7EC10B927@oc8523832656.ibm.com> (raw)
In-Reply-To: <afb86945-7024-c7e1-c966-e120480eded7@vnet.ibm.com> from "Peter Bergner" at Oct 28, 2016 10:02:03 AM

Peter Bergner wrote:
> On 10/28/16 9:15 AM, Ulrich Weigand wrote:
> > It's probably not that important to exactly match objdump
> > behavior here.  B.t.w. how do you even enter a space as
> > separator with the -M option?
> 
> bergner@genoa:~$ objdump -d -M'power5 power6' wait.o  | grep warning
> warning: ignoring unknown -Mpower5 power6 option

OK, well :-)  As I said, it's probably not important to
exactly match *this* detail in the GDB command ...

> But not all arches have descriptions paired with the option name.
> Looking at Pedro's objdump output from before:
> 
> The following ARM specific disassembler options are supported for use with
> the -M switch:
>   reg-names-special-atpcs  Select special register names used in the ATPCS
>   reg-names-atpcs          Select register names used in the ATPCS
>   reg-names-apcs           Select register names used in the APCS
>   reg-names-std            Select register names used in ARM's ISA documentation
>   reg-names-gcc            Select register names used by GCC
>   reg-names-raw            Select raw register names
>   force-thumb              Assume all insns are Thumb insns
>   no-force-thumb           Examine preceding label to determine an insn's type
> 
> This would work well for what you propose, but on power, we just dump them out:
> 
> The following PPC specific disassembler options are supported for use with
> the -M switch:
>  403, 405, 440, 464, 476, 601, 603, 604, 620, 7400, 7410, 7450, 7455,
>  750cl, 821, 850, 860, a2, altivec, any, booke, booke32, cell, com,
>  e200z4, e300, e500, e500mc, e500mc64, e5500, e6500, e500x2, efs, power4,
>  power5, power6, power7, power8, power9, ppc, ppc32, ppc64, ppc64bridge,
>  ppcps, pwr, pwr2, pwr4, pwr5, pwr5x, pwr6, pwr7, pwr8, pwr9, pwrx,
>  spe, titan, vle, vsx, htm, 32, 64

Hmm, I see.  I guess we could have NULL description string for those,
and then the common printing routine could choose the compact output ...

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU/Linux compilers and toolchain
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2016-10-28 18:47 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30  2:14 Peter Bergner
2016-09-30 17:55 ` Ulrich Weigand
2016-10-03 20:25   ` Peter Bergner
2016-10-03 22:25     ` Alan Modra
2016-10-06  3:00       ` Peter Bergner
2016-10-06  4:44         ` Alan Modra
2016-10-06  9:52         ` Pedro Alves
2016-10-06 19:26           ` Peter Bergner
2016-10-07 19:21             ` Ulrich Weigand
2016-10-07 21:01               ` Peter Bergner
2016-10-08 14:39                 ` Ulrich Weigand
2016-10-10 23:28               ` Peter Bergner
2016-10-12  8:08                 ` Ulrich Weigand
2016-10-12 10:46                   ` Pedro Alves
2016-10-11  0:09             ` Pedro Alves
2016-10-11 18:49               ` Peter Bergner
2016-10-12  8:25                 ` Ulrich Weigand
2016-10-27  0:04                   ` Peter Bergner
2016-10-27  9:40                     ` Pedro Alves
2016-10-28 13:47                       ` Peter Bergner
2016-10-28 14:10                         ` Pedro Alves
2016-10-28 14:24                           ` Peter Bergner
2016-10-28 14:30                             ` Pedro Alves
2016-10-28 14:53                               ` Peter Bergner
2016-11-03 11:01                                 ` Pedro Alves
2016-11-03 15:02                                   ` Peter Bergner
2016-11-03 15:06                                     ` Peter Bergner
2016-11-03 16:41                                     ` Ulrich Weigand
2016-11-03 16:49                                       ` Peter Bergner
2016-10-28 12:32                     ` Ulrich Weigand
2016-10-28 13:45                       ` Peter Bergner
2016-10-28 14:15                         ` Ulrich Weigand
2016-10-28 15:02                           ` Peter Bergner
2016-10-28 18:47                             ` Ulrich Weigand [this message]
2016-11-02 23:28                               ` Peter Bergner
2016-10-12 19:35                 ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161028184714.6B7EC10B927@oc8523832656.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=amodra@gmail.com \
    --cc=bergner@vnet.ibm.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox