Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: cgd@broadcom.com
To: aoliva@redhat.com
Cc: "Andrew Cagney" <ac131313@redhat.com>,
	gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: use MIPS NewABI register names when disassembling NewABI code
Date: Fri, 11 Apr 2003 06:03:00 -0000	[thread overview]
Message-ID: <yov5brzdo9k2.fsf@broadcom.com> (raw)
In-Reply-To: aoliva@redhat.com's message of "Fri, 11 Apr 2003 05:43:18 +0000 (UTC)"

At Fri, 11 Apr 2003 05:43:18 +0000 (UTC), "Alexandre Oliva" wrote:
> 	* mips-dis.c (_print_insn_mips): Override reg_names from
> 	disassembler_options.

Uh...  Well...  "I'm not the maintainer, but i'd say no."  8-)

Note the line:

  parse_mips_dis_options (info->disassembler_options);

about 18 lines above your new lines.  It already supports what you
want, but with a different syntax.

> +      tm_print_insn_info.disassembler_options = "NewABI";

"gpr_names=ABI" instead, for values of ABI: 32, n32, 64.

note that, as you probably expect 32 -> oldabi and n32,64 -> newabi.
(default -> oldabi)

IMO it's best to use the correct names for ABIs (i.e., for the
above-named ones or others) so that somebody can add a new ABI easily
to "the obvious place" in GDB, and to the obvious place in the
disassembler, and the right thing should happen automatically.

(It's a real bummer that there's no existing way to return an error
for invalid disassembler options, or i would have coded in some error
reporting.  8-)

(Also note that there's also support for doing the ABI-specific FP
register names, but that's a different option because everybody refers
to them numerically anyway.)


The rest of the gdb disassembler_options setup looks compatible with
the code in the disassembler, but it was a very quick look.  8-)


chris


  parent reply	other threads:[~2003-04-11  6:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08  2:31 Alexandre Oliva
2003-04-08  7:35 ` Andrew Cagney
2003-04-08 11:59   ` Alexandre Oliva
2003-04-08 21:03     ` Andrew Cagney
2003-04-09  3:45       ` Alexandre Oliva
2003-04-09 13:57         ` Daniel Jacobowitz
2003-04-09 14:52         ` Andrew Cagney
2003-04-11  5:43           ` Alexandre Oliva
     [not found]             ` <mailpost.1050039798.9718@news-sj1-1>
2003-04-11  6:03               ` cgd [this message]
2003-04-11  7:47                 ` Alexandre Oliva
2003-04-11 15:06                   ` Andrew Cagney
2003-04-12  0:31                     ` Alexandre Oliva
2003-04-28 21:13                       ` Andrew Cagney

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=yov5brzdo9k2.fsf@broadcom.com \
    --to=cgd@broadcom.com \
    --cc=ac131313@redhat.com \
    --cc=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb-patches@sources.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