Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [patch rfc] Add NUM_REGS pseudo regs to MIPS
Date: Wed, 18 Jun 2003 04:32:00 -0000	[thread overview]
Message-ID: <1030618043229.ZM11543@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@redhat.com> "[patch rfc] Add NUM_REGS pseudo regs to MIPS" (Jun 16, 11:35am)

On Jun 16, 11:35am, Andrew Cagney wrote:

> Per my last post to an old thread.  This adds NUM_REGS pseudo registers 
> to the MIPS.  These pseudo registers, unlike their raw counterparts are 
> `sane'.  They have sensible sizes, offsets, types, ...
> 
> The intent here is to put some distance between the MIPS's messed up raw 
> register buffer and the ABI registers.  As it stands, it doesn't get 
> save/restore right (it works but not by using the ABI registers).  That 
> can follow.
> 
> Tested on mips-elf.
> 
> thoughts?

In light of the recent o32 ABI discussion, I believe the approach
that I used is correct for both the ABI / debug info case as well
as the cli registers case.  I think you should reconsider my patch
before proceeding.

Kevin


  parent reply	other threads:[~2003-06-18  4:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-16 15:35 Andrew Cagney
2003-06-16 15:44 ` Daniel Jacobowitz
2003-06-18  4:32 ` Kevin Buettner [this message]
2003-06-18 16:36   ` Andrew Cagney
2003-06-18 23:54     ` Kevin Buettner
2003-06-21 18:22 ` Andrew Cagney
2003-07-07 20:01 Steve Watt
2003-07-18 22:20 ` Andrew Cagney
2003-07-19  0:13 Steve Watt
2003-07-21 15:26 ` Andrew Cagney
2003-07-21 18:20 Steve Watt
2003-07-21 22:38 ` Andrew Cagney
2003-07-21 22:57 Steve Watt

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=1030618043229.ZM11543@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=ac131313@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