Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [PATCH] Don't attach to 'target_changed' observer in regcache
Date: Thu, 09 Aug 2012 03:11:00 -0000	[thread overview]
Message-ID: <5527210.MOXy64knkR@qiyao.dyndns.org> (raw)
In-Reply-To: <201208081753.q78Hre36003861@glazunov.sibelius.xs4all.nl>

On Wednesday, August 08, 2012 07:53:40 PM Mark Kettenis wrote:
> > The author (Orjan) tried to support "changing the bank select register
> > changes the contents (and meaning) for a whole set of other registers."
> > The requirement is quite specific to Orjan's own port, so the better
> > solution is to attach a function which invalidates all regcache in
> > Orjan's backend, instead of doing it in target-independent part.
> 
> Banked registers aren't really that exotic.  Especially if you realise
> that register windows (SPARC, IA-64) are essentially banked registers.
> 

Banked register doesn't matter here.  "Changing one special register changes 
the whole set of registers", which is exotic, matters.  Are they (banked 
registers) switched by modifying a certain register?  Per my few knowledge on 
SPARC and IA-64, the answer is "No".

The issues of this patch are 1) modifying read-only bits in writable register 
(as Dan pointed out), 2) troubles to Orjan's port.  I can't see any other 
issues of this patch.

-- 
Yao (齐尧)


  reply	other threads:[~2012-08-09  3:11 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 [this message]
2012-08-09  8:12     ` Mark Kettenis
2012-08-09  8:37       ` Yao Qi
2012-08-21 19:39         ` Pedro Alves

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=5527210.MOXy64knkR@qiyao.dyndns.org \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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