Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: paawan oza <paawan1982@yahoo.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb-patches@sourceware.org
Subject: Re: Submition of i386.record.floating.point.patch
Date: Fri, 12 Jun 2009 05:19:00 -0000	[thread overview]
Message-ID: <daef60380906112219m3c2f5453w7fdcd29066fbe3e6@mail.gmail.com> (raw)
In-Reply-To: <277482.46742.qm@web36203.mail.mud.yahoo.com>

Even if you think i386 need this register, it should not be the part
of process record patch.
You can send a patch to make i386 support this register first.

Hui

On Thu, Jun 11, 2009 at 22:59, paawan oza<paawan1982@yahoo.com> wrote:
>
> yes. I know.
> I clarified that i386 also need FTAG, FSTATUS, FCTRL, registers...
> I am also waiting for the clarification from Mark.
> Regards,
> Oza.
>
> --- On Thu, 6/11/09, Hui Zhu <teawater@gmail.com> wrote:
>
>> From: Hui Zhu <teawater@gmail.com>
>> Subject: Re: Submition of i386.record.floating.point.patch
>> To: "paawan oza" <paawan1982@yahoo.com>
>> Cc: "Mark Kettenis" <mark.kettenis@xs4all.nl>, gdb-patches@sourceware.org
>> Date: Thursday, June 11, 2009, 1:15 PM
>> I had post my idea about your patch
>> in before.
>>
>> Thanks,
>> Hui
>>
>> On Thu, Jun 11, 2009 at 15:37, paawan oza<paawan1982@yahoo.com>
>> wrote:
>> >
>> > Hi Hui,
>> > Have you/any-body reviewed floating point patch ?
>> > I am waiting for the review comments, and also the
>> clarification from Mark.
>> > please reply.
>> > Regards,
>> > Oza.
>> >
>> > --- On Fri, 6/5/09, Hui Zhu <teawater@gmail.com>
>> wrote:
>> >
>> >> From: Hui Zhu <teawater@gmail.com>
>> >> Subject: Re: Submition of
>> i386.record.floating.point.patch
>> >> To: "Mark Kettenis" <mark.kettenis@xs4all.nl>
>> >> Cc: gdb-patches@sourceware.org,
>> paawan1982@yahoo.com
>> >> Date: Friday, June 5, 2009, 8:28 AM
>> >> That is great.  Thanks Mark.
>> >>
>> >> Hui
>> >>
>> >> On Fri, Jun 5, 2009 at 10:56, Mark Kettenis<mark.kettenis@xs4all.nl>
>> >> wrote:
>> >> >> Date: Fri, 5 Jun 2009 10:50:25 +0800
>> >> >> From: Hui Zhu <teawater@gmail.com>
>> >> >>
>> >> >> Could someone help us about this?
>> >> >
>> >> > I should be able to, but I'm currently
>> travelling.
>> >>  Should be back next week.
>> >> >
>> >>
>> >
>> >
>> >
>> >
>>
>
>
>
>


  reply	other threads:[~2009-06-12  5:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 15:00 paawan oza
2009-06-12  5:19 ` Hui Zhu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-07-01  3:02 paawan oza
2009-06-30 13:22 paawan oza
2009-06-30 18:52 ` Michael Snyder
2009-06-24 16:22 paawan oza
2009-06-15 15:04 paawan oza
2009-06-12 16:47 paawan oza
2009-06-11 15:18 paawan oza
2009-06-11  7:37 paawan oza
2009-06-11  7:45 ` Hui Zhu
2009-06-08 16:21 paawan oza
2009-06-05 12:05 paawan oza
2009-06-05  2:41 paawan oza
2009-06-05  2:50 ` Hui Zhu
2009-06-05  2:56   ` Mark Kettenis
2009-06-05  2:58     ` Hui Zhu
2009-06-03  4:03 paawan oza
2009-06-02 17:58 paawan oza
2009-06-03  2:58 ` Hui Zhu
2009-06-01 14:55 paawan oza
2009-06-02  6:58 ` Hui Zhu
2009-06-04 22:18   ` Hui Zhu
2009-05-31 18:51 submition " paawan oza
2009-06-01  2:50 ` Hui Zhu
2009-05-31 11:49 paawan oza
2009-05-31 15:44 ` Hui Zhu
2009-05-31 18:02 ` Mark Kettenis

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=daef60380906112219m3c2f5453w7fdcd29066fbe3e6@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --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