From: paawan oza <paawan1982@yahoo.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb ml <gdb@sourceware.org>
Subject: Re: MMX & Floating point insn suport for reversible debugging
Date: Fri, 15 May 2009 14:16:00 -0000 [thread overview]
Message-ID: <795073.59477.qm@web36208.mail.mud.yahoo.com> (raw)
Thank you for your inputs.
I will try to post question more clearly : )
my question was :
Do we need to record floating point flags (C0,C1,C2 and c3) along with floating point registers ?
Regards,
Oza.
--- On Thu, 5/14/09, Hui Zhu <teawater@gmail.com> wrote:
> From: Hui Zhu <teawater@gmail.com>
> Subject: Re: MMX & Floating point insn suport for reversible debugging
> To: "paawan oza" <paawan1982@yahoo.com>
> Cc: "gdb ml" <gdb@sourceware.org>
> Date: Thursday, May 14, 2009, 12:41 PM
> On Thu, May 14, 2009 at 00:44, paawan
> oza <paawan1982@yahoo.com>
> wrote:
> >
> > I have gone through i387-tdep.c.
> > and I have come up with following doubts.
> >
> > here I start adding floating point register
> support.
> > I think curerntly it records the memory
> >
> > so remaining thing for floating point is store
> > registers st0 to st7.
> >
> >
> >> > code to be added here...
> >> > /* floats */
> >> > /* It just record the memory change
> of
> >> instrcution. */
> >> > case 0xd8:
> >> > case 0xd9:
> >> > case 0xda:
> >> > case 0xdb:
> >> > case 0xdc:
> >> > case 0xdd:
> >> > case 0xde:
> >> > case 0xdf:
> >> >
> >> >
> > do we need to collect affect FPU flags !!
>
> If gdb can output and set this flags, you need to do it.
> And I suggest you post more clear information about your
> question that
> you know when you have question with it. It will make
> people reply
> you mail easyly, right? :)
>
> >
> > and another thing is ;
> > take floating point insn
> > opcode mnemnic desc
> > DE F9 FDIVP Divide ST(1) by ST(0),
> > store result in ST(1),
> and
> > pop the register
> stack.
> >
> > I do not think code is taking care of 2 bytes
> floating
> > instruction..
> > I suspoe ModR/M and SIB byte encoding is taken care
> > with respect to floating point.
>
> Why you can't put the code for "DE F9" in:
> >> > case 0xde:
>
>
> Thanks,
> Hui
>
next reply other threads:[~2009-05-15 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 14:16 paawan oza [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-13 16:44 paawan oza
2009-05-14 7:11 ` Hui Zhu
2009-05-13 16:17 paawan oza
2009-05-13 16:38 ` 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=795073.59477.qm@web36208.mail.mud.yahoo.com \
--to=paawan1982@yahoo.com \
--cc=gdb@sourceware.org \
--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