Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: paawan oza <paawan1982@yahoo.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Hui Zhu <teawater@gmail.com>,
	  "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: final i386.floating.record.patch
Date: Thu, 10 Sep 2009 01:13:00 -0000	[thread overview]
Message-ID: <88392.51303.qm@web112502.mail.gq1.yahoo.com> (raw)
In-Reply-To: <4AA6F425.4010100@vmware.com>

Thank you Michael.
I am still waiting for the papers to arrive.
I do not have much idea, how much more we need to wait :(
once I get the papers and get them signed, we are ready to go :)
Regards,
Oza.


--- On Wed, 9/9/09, Michael Snyder <msnyder@vmware.com> wrote:

> From: Michael Snyder <msnyder@vmware.com>
> Subject: Re: final i386.floating.record.patch
> To: "paawan oza" <paawan1982@yahoo.com>
> Cc: "Hui Zhu" <teawater@gmail.com>, "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> Date: Wednesday, September 9, 2009, 5:47 AM
> paawan oza wrote:
> > Hu Hui,
> > please find the ChageLog and floating point patch
> attached as you suggested.
> > Sorry for not pasting it in email-body becasue of
> space and tabs issues.
> > Do we need to update wiki?
> > Regards,
> > Oza.
> 
> To help keep this patch alive (while waiting for Oza's
> copyright
> assignment), I have taken the liberty of merging and
> updating it
> against today's cvs head (Sept. 8, 2009).
> 
> 2009-08-21  Oza Pawandeep  <paawan1982@yahoo.com>
> 
>         * i386-tdep.c:  Support
> for floating point recording.
>         Records and Replay the i386
> floating point registers,
>         of i387 FPU.
> 
> 
> 
> -----Inline Attachment Follows-----
> 
> 




  reply	other threads:[~2009-09-10  1:13 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2009-09-26  9:33   ` paawan oza
2009-12-10  7:55 ` Hui Zhu
  -- strict thread matches above, loose matches on Subject: below --
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-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-05  1:34         ` Michael Snyder
2009-08-05 13:48           ` 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=88392.51303.qm@web112502.mail.gq1.yahoo.com \
    --to=paawan1982@yahoo.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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