From: Michael Snyder <msnyder@vmware.com>
To: paawan oza <paawan1982@yahoo.com>
Cc: Hui Zhu <teawater@gmail.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: final i386.floating.record.patch
Date: Wed, 05 Aug 2009 01:34:00 -0000 [thread overview]
Message-ID: <4A78E14C.2070608@vmware.com> (raw)
In-Reply-To: <509767.4697.qm@web112517.mail.gq1.yahoo.com>
paawan oza wrote:
> Hi Hui,
>
> please find my analysis as follows.
>
> following are the registers which you may find it different.
>
> fstat
> ftag
> fiseg
> fioff
> foseg
> fooff
> fop
>
> In my opinion, we do not need to record all these registers. because these registers are purly depends on instruction's execution status in FPU unit.
>
>
> for e.g.
> fop register stores te last opcode executed by x87 FPU unit.
> fstat register may contain c0, c1, c2, c3 flag status...
>
> why we dont need to record, because even if we reply the recod...
> Anyway these register are going to be change by FPU HW unit based on any fp insn's nature and its execution. (next insn which FPU is going to execute)
>
> so it doesnt make much sense to store it, because even if we restore it, FPU unit doesnt use them directly, but FPU HW sets them after executing current fp insn. so anyway they are going to reset as soon as FPU executes next insn.
>
> but still if you feel that we must record those registers because user might want to observe those registers, then I can do that.
>
> please let me know you opinion about it.
It may be that saving the registers is not purely necessary, but
we are not just a simulator -- we are a debugger. The user might
be confused if he steps backward and sees that the register did not
change.
So I think we should preserve it and revert it.
next prev parent reply other threads:[~2009-08-05 1:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 13:06 paawan oza
2009-08-04 13:58 ` Hui Zhu
2009-08-04 14:18 ` paawan oza
2009-08-04 14:26 ` paawan oza
2009-08-04 14:43 ` Hui Zhu
2009-08-04 17:59 ` paawan oza
2009-08-05 1:29 ` Hui Zhu
2009-08-07 8:39 ` regarding recording of registers paawan oza
2009-08-05 1:34 ` Michael Snyder [this message]
2009-08-05 13:48 ` final i386.floating.record.patch paawan oza
-- strict thread matches above, loose matches on Subject: below --
2009-08-21 16:59 paawan oza
2009-08-23 1:32 ` Hui Zhu
2009-08-23 3:00 ` Michael Snyder
2009-08-23 9:04 ` paawan oza
2009-08-23 9:29 ` paawan oza
2009-09-09 0:19 ` Michael Snyder
2009-09-10 1:13 ` paawan oza
2009-09-26 9:33 ` paawan oza
2009-12-10 7:55 ` Hui Zhu
2009-08-18 15:22 paawan oza
2009-08-19 2:17 ` Hui Zhu
2009-08-19 2:44 ` Hui Zhu
2009-08-07 7:25 paawan oza
2009-08-07 15:50 ` Hui Zhu
2009-08-16 21:41 ` Michael Snyder
2009-08-17 9:17 ` Hui Zhu
2009-08-17 16:16 ` paawan oza
2009-08-03 14:56 paawan oza
2009-08-03 20:04 ` Michael Snyder
2009-08-04 3:20 ` Hui Zhu
2009-08-04 13:03 ` paawan oza
2009-07-29 18:34 paawan oza
2009-07-30 6:24 ` Michael Snyder
2009-07-30 18:09 ` paawan oza
2009-08-03 14:59 ` paawan oza
2009-08-03 20:07 ` Michael Snyder
2009-07-27 1:09 i386.record.floating.point.patch : with more testing and assurity Michael Snyder
2009-07-29 18:30 ` final i386.floating.record.patch paawan oza
2009-07-29 22:01 ` Michael Snyder
2009-07-30 0:44 ` Michael Snyder
2009-07-30 18:00 ` paawan oza
2009-07-30 21:13 ` Michael Snyder
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=4A78E14C.2070608@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=paawan1982@yahoo.com \
--cc=teawater@gmail.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