From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9461 invoked by alias); 7 Feb 2003 15:46:35 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 9454 invoked from network); 7 Feb 2003 15:46:34 -0000 Received: from unknown (HELO kerberos.suse.cz) (195.47.106.10) by 172.16.49.205 with SMTP; 7 Feb 2003 15:46:34 -0000 Received: from chimera.suse.cz (chimera.suse.cz [10.20.0.2]) by kerberos.suse.cz (SuSE SMTP server) with ESMTP id 759E759D36E; Fri, 7 Feb 2003 16:46:33 +0100 (CET) Received: from suse.cz (naga.suse.cz [10.20.1.16]) by chimera.suse.cz (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with ESMTP id h17FkX417345; Fri, 7 Feb 2003 16:46:33 +0100 X-Authentication-Warning: chimera.suse.cz: Host naga.suse.cz [10.20.1.16] claimed to be suse.cz Message-ID: <3E43D4D9.20509@suse.cz> Date: Fri, 07 Feb 2003 15:46:00 -0000 From: Michal Ludvig Organization: SuSE CR User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: cs, cz, en MIME-Version: 1.0 To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: regcache (Re: GDB respin) References: <200302031615.h13GFVP26477@duracef.shout.net> <3E3EA35D.3080300@redhat.com> <3E427169.5010702@suse.cz> <3E42A5F8.9080708@redhat.com> In-Reply-To: <3E42A5F8.9080708@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00151.txt.bz2 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