Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: gdb-patches@sources.redhat.com, Paul Brook <paul@codesourcery.com>
Subject: Re: [patch] registers beginning with '$'
Date: Tue, 08 Mar 2005 13:43:00 -0000	[thread overview]
Message-ID: <20050308134308.GD7417@nevyn.them.org> (raw)
In-Reply-To: <422D72C9.1060206@codesourcery.com>

On Tue, Mar 08, 2005 at 09:39:21AM +0000, Nathan Sidwell wrote:
> Daniel Jacobowitz wrote:
> >On Thu, Feb 10, 2005 at 10:32:29AM +0000, Nathan Sidwell wrote:
> >
> >>Hi,
> >>I had the misfortune to port to an architecture where register names
> >>all start with a '$' and the pc reg is '$PC'.  This patch fixes expression
> >>printing of registers so that such names don't result in '$$name' being
> >>printed.  It fixes register name lookup so that the leading '$' need not
> >>be specified (several places strip leading '$' on the name to be looked
> >>up).  It also makes the register name lookup case insensitive.
> >>
> >>I also attach testsuite patches to allow $pc or $PC as the pc name.
> >>
> >>built and tested on i686-pc-linux-gnu, and an unreleased architecture, ok?
> >
> >
> >This one I'm less sure about.  If you tell GDB the register names do
> >not contain '$', what output is wrong?
> 
> The output from the 'info regs' command will then not have the '$'.

Then you should provide gdbarch_print_registers_info; you can make this
look however you want on a per-target basis.
 
-- 
Daniel Jacobowitz
CodeSourcery, LLC


      reply	other threads:[~2005-03-08 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 15:27 Nathan Sidwell
2005-03-07 22:58 ` Daniel Jacobowitz
2005-03-08  9:39   ` Nathan Sidwell
2005-03-08 13:43     ` Daniel Jacobowitz [this message]

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=20050308134308.GD7417@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nathan@codesourcery.com \
    --cc=paul@codesourcery.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