From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: The ari hits
Date: Fri, 28 Feb 2003 17:54:00 -0000 [thread overview]
Message-ID: <3E5FA2D8.3020706@redhat.com> (raw)
In-Reply-To: <20030228015238.GA17237@nevyn.them.org>
> On Thu, Feb 27, 2003 at 05:09:46PM -0500, Andrew Cagney wrote:
>
>> Daniel,
>>
>> The files you recently committed trip the ARI. Can you please check
>> this out.
>>
>> Andrew
>>
>> http://sources.redhat.com/gdb/current/ari/
>
>
> Thanks for reminding me; this patch fixes them. Almost obvious except
> for a bit that I want your opinion on - the hint on the ARI
> says to use register_size but I'm not convinced that's right. Is
> gdbarch_register_size always big enough that I don't need to use
> gdbarch_register_raw_size?
You're correct, however, so is the comment - use register_size() (not
gdbarch_register_size). The problem is that I forgot to add that
function to regcache.[ch] :-( I've just done this.
There is also a bigger problem here. Because some targets still have
differring raw and cooked register sizes (read MIPS), things get messy.
frame_register() returns a `cooked' register value so, for the moment,
I'd use:
REGISTER_VIRTUAL_SIZE (...) /* OK */
(the ``/* OK */'' gags the ARI) and add a comment.
sorry about this,
Andrew
next prev parent reply other threads:[~2003-02-28 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 22:07 Andrew Cagney
2003-02-28 1:52 ` Daniel Jacobowitz
2003-02-28 17:54 ` Andrew Cagney [this message]
2003-02-28 17:59 ` Daniel Jacobowitz
2003-03-02 2:01 ` Andrew Cagney
2003-03-02 3:14 ` Daniel Jacobowitz
2003-03-03 21:49 ` Daniel Jacobowitz
2003-10-10 2:52 The ARI hits Andrew Cagney
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=3E5FA2D8.3020706@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.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