Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Elena Zannoni <ezannoni@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] ppc: include register numbers in gdbarch_tdep structure.
Date: Sun, 09 Dec 2001 15:09:00 -0000	[thread overview]
Message-ID: <3C13EF3E.3000102@cygnus.com> (raw)
In-Reply-To: <1011209212323.ZM18906@ocotillo.lan>

> Though I do wonder if it was really necessary to move register
> numbers which are truly constant to the gdbarch_tdep struct.  BTW,
> this wouldn't bother me so much if we could use inline functions
> in C.


Based on the pains I'm experiencing with going through trying to get 
some MMX changes for x86 in a state where I can submit them, I suspect 
it is the better of the alternatives.

The x86 has a mix and that is just confusing.  I don't know what can 
change and what can't change and what secret relationships there are 
between the constants and variables.

On paper, it should be possible to describe the entire raw regcache 
using constants.  I'm finding that, in reality, until all the relevant 
framework is fleshed out (eg my regcache breakage, everything 
multi-arch) it isn't really possible.  Sigh.

enjoy,
Andrew



  parent reply	other threads:[~2001-12-09 23:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-09 11:58 Elena Zannoni
2001-12-09 13:24 ` Kevin Buettner
2001-12-09 13:38   ` Elena Zannoni
2001-12-09 15:09   ` Andrew Cagney [this message]
2001-12-12 12:16     ` Mark Kettenis
2001-12-10 11:33 ` Michael Snyder
2001-12-10 12:25   ` Kevin Buettner
2001-12-10 12:41     ` Elena Zannoni
2001-12-10 13:22       ` Kevin Buettner
2001-12-10 14:34         ` 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=3C13EF3E.3000102@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=ezannoni@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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