From: Fred Fish <fnf@ninemoons.com>
To: gdb-patches@sources.redhat.com
Cc: fnf@ninemoons.com
Subject: Re: [PATCH] Remove some hardwired assumptions about register sets
Date: Tue, 23 Dec 2003 01:51:00 -0000 [thread overview]
Message-ID: <200312221851.10629.fnf@ninemoons.com> (raw)
In-Reply-To: <200312170614.hBH6Ebtl003033@fred.ninemoons.com>
On Tuesday 16 December 2003 23:14, Fred Fish wrote:
> This patch removes some hard coded assumptions about the sizes of the
> various processor specific register sets, and also allows them to be
> of different sizes if necessary.
>
> Comments?
Except for my own followup, there haven't been any comments about this
patch.
I propose that if there are no objections by this weekend that the
patch should be checked in, after the previously noted fix is made of
course.
-Fred
next prev parent reply other threads:[~2003-12-23 1:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 6:14 Fred Fish
2003-12-17 6:22 ` Fred Fish
2003-12-23 1:51 ` Fred Fish [this message]
2003-12-23 2:03 ` Daniel Jacobowitz
2004-01-02 19:28 ` Andrew Cagney
2004-01-02 19:31 ` Daniel Jacobowitz
2004-01-02 23:12 ` Fred Fish
2004-01-05 15:50 ` Andrew Cagney
2003-12-23 11:30 ` Mark Kettenis
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=200312221851.10629.fnf@ninemoons.com \
--to=fnf@ninemoons.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