Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Basic structure to describe register formats
Date: Fri, 01 Feb 2002 13:21:00 -0000	[thread overview]
Message-ID: <20020201162042.A20026@nevyn.them.org> (raw)
In-Reply-To: <3C5B0438.6010005@cygnus.com>

On Fri, Feb 01, 2002 at 04:10:16PM -0500, Andrew Cagney wrote:
> Almost approved,  I've been pokeing at random targets that once worked 
> and they have now all been broken by multi-arch.
> 
> >@@ -0,0 +1,28 @@
> >+name:arm
> >+resume:r11,sp,pc
> >+4:r0
> >+4:r1
> >+4:r2
> 
> 
> My only quarm is with this.  It extends the G packet definition a little 
> - lines with a leading letter get ignored just like comments and blanks. 
>  Correct?

Do we even have such a definition?  I didn't think we did yet.

If so, then yes, I think that's a good extension.  Also I would commit
it with the number in bits rather than bytes.

> Any way I think EXPEDITE to better word for describing what is to be 
> done with those registers.  SID uses that word to describe this exact 
> same list.

That's a good word for what's going on here, I quite like it.  OK with
that change?

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-02-01 21:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01 12:22 Daniel Jacobowitz
2002-02-01 13:10 ` Andrew Cagney
2002-02-01 13:21   ` Daniel Jacobowitz [this message]
2002-02-01 13:50     ` Andrew Cagney
2002-02-01 14:09       ` Daniel Jacobowitz
2002-02-01 15:28         ` Andrew Cagney
2002-02-01 14:01     ` Frank Ch. Eigler

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=20020201162042.A20026@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@cygnus.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