From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org, Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [PATCH] Don't attach to 'target_changed' observer in regcache
Date: Tue, 21 Aug 2012 19:39:00 -0000 [thread overview]
Message-ID: <5033E3EB.60004@redhat.com> (raw)
In-Reply-To: <1488047.W4eyA0a8U4@qiyao.dyndns.org>
On 08/09/2012 09:36 AM, Yao Qi wrote:
> I am thinking that we may add a new gdbarch hook function 'register_changed
> (int regnum)'. In default, it invalidates all regcaches, and backend can
> override it to do something optimally. At least, we don't have to invalidate
> all regcache on some ports, such as x86, tic6x.
gdbarch is only useful for the cases gdb can hardcode. it is not
sufficient in the cases the target feeds gdb a target description with
more registers than gdb knows the core architecture of the running
target has.
--
Pedro Alves
prev parent reply other threads:[~2012-08-21 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 7:17 Yao Qi
2012-08-02 14:46 ` Pedro Alves
2012-08-02 15:40 ` Yao Qi
2012-08-08 17:54 ` Mark Kettenis
2012-08-09 3:11 ` Yao Qi
2012-08-09 8:12 ` Mark Kettenis
2012-08-09 8:37 ` Yao Qi
2012-08-21 19:39 ` Pedro Alves [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=5033E3EB.60004@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=yao@codesourcery.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