Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: Supplying regsets containing pseudoregisters
Date: Wed, 09 Jun 2004 21:03:00 -0000	[thread overview]
Message-ID: <vt2r7so5trv.fsf@zenia.home> (raw)
In-Reply-To: <vt2wu2g63ox.fsf@zenia.home>

Jim Blandy <jimb@redhat.com> writes:

> Andrew Cagney <cagney@gnu.org> writes:
> > It sounds like the regcache layout needs to be changed.  I'd break the
> > raw EV registers down into hi:lo pairs so that each part can be
> > supplied separatly - this appears to more closely reflect the
> > underlying implementation.
> 
> Okay.  This is what I'd started doing thinking of it as a workaround,
> so it works for me.

Actually, maybe not.

The sim provides access to the GPRs as full 64-bit values.  It calls
sim_fetch_register, gets 64 bits, and then calls supply_register on
the full 64 bits.

But core files and libthread_db operate on gregset_t values, which
contain only the lower 32 bits of the GPRs.  The regset 'supply'
functions want to call regcache_raw_supply on only the lower halves.

So does gdbsim_fetch_register need to be tweaked somehow?  How would
it know how to distribute the 64-bit value across high/low pairs?

Do I need to use separate regcache layouts for sim and native?  How
would I even do that?


  reply	other threads:[~2004-06-09 21:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-08 23:46 Jim Blandy
2004-06-09 15:43 ` Andrew Cagney
2004-06-09 17:29   ` Jim Blandy
2004-06-09 21:03     ` Jim Blandy [this message]
2004-06-10 16:28       ` 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=vt2r7so5trv.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=cagney@gnu.org \
    --cc=gdb@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