From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] Avoid MIPS port breakage on large registers
Date: Wed, 13 Jun 2007 17:25:00 -0000 [thread overview]
Message-ID: <20070613172549.GE1023@caradoc.them.org> (raw)
In-Reply-To: <20070521130529.GA1392@caradoc.them.org>
On Mon, May 21, 2007 at 09:05:29AM -0400, Daniel Jacobowitz wrote:
> 2007-05-21 Daniel Jacobowitz <dan@codesourcery.com>
>
> * mips-tdep.c (mips_print_register): Remove unused ALL argument.
> (print_gp_register_row): Stop before printing a register bigger
> than the ABI register size.
> (mips_print_registers_info): Update call to mips_print_register.
Checked in.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-06-13 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 13:05 Daniel Jacobowitz
2007-05-21 14:01 ` Maciej W. Rozycki
2007-05-21 14:09 ` Daniel Jacobowitz
2007-06-13 17:25 ` Daniel Jacobowitz [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=20070613172549.GE1023@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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