From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-34472-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 13404 invoked by alias); 23 May 2009 13:11:48 -0000
Received: (qmail 13392 invoked by uid 22791); 23 May 2009 13:11:46 -0000
X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from web36206.mail.mud.yahoo.com (HELO web36206.mail.mud.yahoo.com) (209.191.68.232)     by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Sat, 23 May 2009 13:11:41 +0000
Received: (qmail 45968 invoked by uid 60001); 23 May 2009 13:11:40 -0000
Message-ID: <954950.45742.qm@web36206.mail.mud.yahoo.com>
Received: from [123.238.26.52] by web36206.mail.mud.yahoo.com via HTTP; Sat, 23 May 2009 06:11:39 PDT
Date: Sat, 23 May 2009 13:11:00 -0000
From: paawan oza <paawan1982@yahoo.com>
Subject: Re: push and pop of FPU stack ; record st registers
To: Hui Zhu <teawater@gmail.com>
Cc: gdb ml <gdb@sourceware.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2009-05/txt/msg00158.txt.bz2


sure, I will focus on make it work first : )

--- On Sat, 5/23/09, Hui Zhu <teawater@gmail.com> wrote:

> From: Hui Zhu <teawater@gmail.com>
> Subject: Re: push and pop of FPU stack ; record st registers
> To: "paawan oza" <paawan1982@yahoo.com>
> Cc: "gdb ml" <gdb@sourceware.org>
> Date: Saturday, May 23, 2009, 5:31 PM
> I think make the function can run is
> the first job,
> 
> Hui
> 
> On Sat, May 23, 2009 at 14:17, paawan oza <paawan1982@yahoo.com>
> wrote:
> >
> > yes. I can record all st0 to st7 registers. that is
> not a problem.
> > but, at every insn which push/pop FPU stack, if we
> record all st0 to st7, we will be occupying too much of
> record memory.
> > (memory usage will be more for our records)
> >
> > I was just thinking of optimizing it with some cache.
> > but at the moment I think I can go ahead with plain
> implementation of recording st0 to st7.
> >
> > Regards,
> > Oza.
> >
> >
> >
> > --- On Sat, 5/23/09, Hui Zhu <teawater@gmail.com>
> wrote:
> >
> >> From: Hui Zhu <teawater@gmail.com>
> >> Subject: Re: push and pop of FPU stack ; record st
> registers
> >> To: "paawan oza" <paawan1982@yahoo.com>
> >> Cc: "gdb ml" <gdb@sourceware.org>
> >> Date: Saturday, May 23, 2009, 9:34 AM
> >> You cannot record st0 to st7?
> >>
> >> Hui
> >>
> >> On Fri, May 22, 2009 at 23:43, paawan oza <paawan1982@yahoo.com>
> >> wrote:
> >> >
> >> > Hi,
> >> >
> >> > the instructions such as;
> >> > fld1, which pushes fpu stack and insn faddp
> pops
> >> registers stack,
> >> > we need to record all st0 to st7 registers.
> because
> >> all will be changed on push/pop.
> >> > as pushing/popping changes all the registers,
> at such
> >> insns (which does push/pop) we record all st0 to
> st7
> >> registers that may affect the performance.
> >> >
> >> > currently I can not think of any alternative
> >> > (may be we cache registers all the time and
> we record
> >> only those which may change) but by doing that we
> only save
> >> memory. performance is still question :(
> >> >
> >> > Does anybody have any other suggestion ?
> >> >
> >> > Regards,
> >> > Oza.
> >> >
> >> >
> >> >
> >> >
> >>
> >
> >
> >
> >
>