From: Andrew Cagney <ac131313@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: register_offset_hack() vs REGISTER_BYTE()
Date: Fri, 02 May 2003 23:16:00 -0000 [thread overview]
Message-ID: <3EB2FC35.6010603@redhat.com> (raw)
In-Reply-To: <1030502225744.ZM30793@localhost.localdomain>
> For MIPS register numbers in [0, NUM_REGS), I'm going to make
> mips_register_virtual_type() always return a type whose size is the same as
> that currently returned by mips_register_raw_size().
Yes!!! That should have always been that way.
> I'll introduce pseudo
> registers for those that actually need different virtual sizes. (I've
> turned mips o32 floating point registers into pseudo registers already and
> it seems to work...)
Yep.
> This'll allow me to eliminate the MIPS REGISTER_BYTE and REGISTER_RAW_SIZE
> definitions. Plus some other stuff too. E.g, I've already gotten rid of
> mips_register_convert_to_type() and mips_register_convert_from_type(). I
> think mips_register_convert_to_virtual() and mips_register_convert_to_raw()
> will end up going away too.
Don't stop there. It should be possible to trim it down to something like:
- register_type
- num_regs
- num_pseudo_regs
- register_name
(looking at the d10v I've a few more to eliminate).
This means that a huge chunk of nastiness can finally be expunged from
GDB. Ya!
Andrew
prev parent reply other threads:[~2003-05-02 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 0:38 Kevin Buettner
2003-05-02 0:58 ` Andrew Cagney
2003-05-02 1:09 ` Kevin Buettner
2003-05-02 1:30 ` Andrew Cagney
2003-05-02 22:26 ` Andrew Cagney
2003-05-02 22:57 ` Kevin Buettner
2003-05-02 23:16 ` Andrew Cagney [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=3EB2FC35.6010603@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).