Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: paawan oza <paawan1982@yahoo.com>
Cc: gdb ml <gdb@sourceware.org>
Subject: Re: push and pop of FPU stack ; record st registers
Date: Sat, 23 May 2009 12:01:00 -0000	[thread overview]
Message-ID: <daef60380905230501j5c294216q9800c2a739b3272@mail.gmail.com> (raw)
In-Reply-To: <130576.31017.qm@web36202.mail.mud.yahoo.com>

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.
>> >
>> >
>> >
>> >
>>
>
>
>
>


  reply	other threads:[~2009-05-23 12:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-23  6:17 paawan oza
2009-05-23 12:01 ` Hui Zhu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-23 13:11 paawan oza
2009-05-22 15:43 paawan oza
2009-05-23  4:04 ` Hui Zhu

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=daef60380905230501j5c294216q9800c2a739b3272@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=paawan1982@yahoo.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