Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michal Ludvig <mludvig@suse.cz>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: regcache (Re: GDB respin)
Date: Fri, 07 Feb 2003 15:46:00 -0000	[thread overview]
Message-ID: <3E43D4D9.20509@suse.cz> (raw)
In-Reply-To: <3E42A5F8.9080708@redhat.com>

Andrew Cagney wrote:
> 
>> I'm about to convert x86-64 target to use regcache, but am not sure 
>> what must be done for it. Could someone please briefly explain me what 
>> is regcache all about and what must be changed in order to have the 
>> target regcache-compilant?
> 
> 
> Where previously the code wrote (directly or implicitly) to a global 
> buffer, it how is given an explicit object (the regcache).
> 
> You can use any *cooked*{read,write}* function you want in regcache.h. 
> Typically the transformation is very direct: write_register() -> 
> regcache_cooked_write().

What's the difference between cooked and non-cooked function? As far as 
I noticed, i386 target doesn't use cooked functions at all...

How do I store/read for example a long double, that is passed in two X87 
registers? With regbuf it's stored in a place for FP0 and FP0+8 in 
registers array. Will it come to a single slot of a regcache now?

Michal Ludvig
-- 
* SuSE CR, s.r.o     * mludvig@suse.cz
* (+420) 296.545.373 * http://www.suse.cz


  parent reply	other threads:[~2003-02-07 15:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 16:15 GDB respin Michael Elizabeth Chastain
2003-02-03 17:14 ` Andrew Cagney
2003-02-03 18:08   ` Elena Zannoni
2003-02-06 14:30   ` regcache (Re: GDB respin) Michal Ludvig
2003-02-06 18:14     ` Andrew Cagney
2003-02-06 23:24       ` [PATCH] " Mark Kettenis
2003-02-07 15:46       ` Michal Ludvig [this message]
2003-02-09 10:20         ` Andrew Cagney
2003-02-10 21:26       ` Michal Ludvig
2003-02-10 22:42         ` Mark Kettenis
2003-02-11 16:31           ` Andrew Cagney
2003-02-11 23:12             ` Michal Ludvig

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=3E43D4D9.20509@suse.cz \
    --to=mludvig@suse.cz \
    --cc=ac131313@redhat.com \
    --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