Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: paawan oza <paawan1982@yahoo.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
	  "pedro@codesourcery.com" <pedro@codesourcery.com>,
	 "teawater@gmail.com" <teawater@gmail.com>,
	  "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: i386.record.floating.point.patch : with more testing and assurity
Date: Fri, 03 Jul 2009 21:52:00 -0000	[thread overview]
Message-ID: <4A4E7D05.8080608@vmware.com> (raw)
In-Reply-To: <801902.97924.qm@web112506.mail.gq1.yahoo.com>

paawan oza wrote:
> Hi,
> 
> In My understanding the point was like below.
> in the patch there were following register extended in enumeration in 
> i386-tdep.h
> 
> I386_FSTAT,
> I386_FTAG,       
> I386_FISEG,
> I386_FIOFF,
> I386_FOSEG,
> I386_FOOFF,
> I386_FOP
> 
> 
> According to Hui in some of his previous mails...his idea was
>> FCTRL, FOP and so on are the fp reg of amd64.  For now, prec is still
>> not support amd64 And amd64's support are in amd64-tedp.... files.  >Change i386_regnum is not a good idea. I suggest you divide fp patch to 2 >parts. One is for i386, the other for amd64. For now, just send i386 patch >for review.  And send amd64 patch when prec support amd64"
> 
> 
> while, my idea/understanding is:
> FCTRL, FOP registers are not only a part of amd64, but also part of i386 (x87 FPU unit) also.
> so according to me these registers are part of i386 also and it needed to be also in i386-tdep.h.
> 
> Regards,
> Oza.

I'm not sure why you want to add those constants to i386-tdep.h,
when the rest of your patch does not seem to use them.


  reply	other threads:[~2009-07-03 21:52 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03 18:55 paawan oza
2009-07-03 21:52 ` Michael Snyder [this message]
     [not found] <992589.56162.qm@web112513.mail.gq1.yahoo.com>
2009-07-26 19:10 ` Mark Kettenis
  -- strict thread matches above, loose matches on Subject: below --
2009-07-26 14:27 paawan oza
2009-07-26 22:51 ` Michael Snyder
2009-07-27  1:09 ` Michael Snyder
2009-07-27  2:33 ` Samuel Bronson
2009-07-06 19:09 paawan oza
2009-07-06 19:05 paawan oza
2009-07-08  9:00 ` Hui Zhu
2009-07-12  9:52 ` Michael Snyder
2009-07-12 18:12   ` Michael Snyder
2009-07-06 19:03 paawan oza
2009-07-06 19:01 paawan oza
2009-07-04  5:19 paawan oza
2009-07-05 10:15 ` Hui Zhu
2009-07-02  7:40 paawan oza
2009-07-02  3:39 paawan oza
2009-07-02  3:34 paawan oza
2009-07-01 16:17 paawan oza
2009-07-05 18:33 ` Mark Kettenis
2009-07-01 16:02 paawan oza
2009-07-01 16:14 ` Mark Kettenis
2009-07-01 16:01 paawan oza
2009-07-01 15:59 paawan oza
2009-07-02  2:02 ` Hui Zhu
2009-06-30 15:05 paawan oza
2009-07-01  5:53 ` Hui Zhu
2009-07-12 11:12 ` Michael Snyder
2009-07-12 17:47   ` paawan oza
2009-07-13  0:38     ` Michael Snyder
2009-07-13 17:03       ` Hui Zhu
2009-07-13 20:16         ` Michael Snyder
2009-07-15  9:21           ` Hui Zhu
2009-07-19  3:27             ` paawan oza
2009-07-18 23:36           ` paawan oza
2009-06-30 13:23 paawan oza
2009-06-30 13:38 ` Pedro Alves
2009-06-30 13:42 ` Mark Kettenis
2009-06-04 14:50 paawan oza

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=4A4E7D05.8080608@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=paawan1982@yahoo.com \
    --cc=pedro@codesourcery.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