From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc][4/13] Eliminate read_register: read_register in deprecated_mips_set_processor_regs_hack
Date: Fri, 08 Jun 2007 12:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64N.0706081323450.2732@blysk.ds.pg.gda.pl> (raw)
In-Reply-To: <200706072058.l57KwV3u019800@d12av02.megacenter.de.ibm.com>
On Thu, 7 Jun 2007, Ulrich Weigand wrote:
> one more weird global register access in a tdep file:
> deprecated_mips_set_processor_regs_hack in mips-tdep.c.
This register is read-only, so it does not matter which copy you read.
;-)
> (Not sure if this is still required, or if it could be replaced by
> the new XML register mechanism ...)
Well, if the latter provides similar means. I have extensive changes
pending for deprecated_mips_set_processor_regs_hack() and this access
definitely has to stay.
Maciej
next prev parent reply other threads:[~2007-06-08 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 20:58 Ulrich Weigand
2007-06-08 12:28 ` Maciej W. Rozycki [this message]
2007-06-12 14:19 ` Daniel Jacobowitz
2007-06-12 14:50 ` Maciej W. Rozycki
2007-06-12 15:05 ` Daniel Jacobowitz
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=Pine.LNX.4.64N.0706081323450.2732@blysk.ds.pg.gda.pl \
--to=macro@linux-mips.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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