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: Pedro Alves <pedro@codesourcery.com>,
	Mark Kettenis <mark.kettenis@xs4all.nl>,
	 	Michael Snyder <msnyder@vmware.com>,
	gdb-patches@sourceware.org
Subject: Re: i386.record.floating.point.patch : with more testing and assurity
Date: Thu, 02 Jul 2009 02:02:00 -0000	[thread overview]
Message-ID: <daef60380907011901t30682c3fsaeb0d18be3aa0260@mail.gmail.com> (raw)
In-Reply-To: <656840.90117.qm@web112508.mail.gq1.yahoo.com>

On Wed, Jul 1, 2009 at 23:59, paawan oza<paawan1982@yahoo.com> wrote:
>
> Hi Hui,
>
> As I clarified earlier,
> these registers are already supported and extended by gdb much before this patch.
> all floating point registers are already supported by gdb
> (info floats/info all-registers command gives it)
>
> My aim is : only to make sure that whenever any floating point insn gets executed, we record the registers
> (no matter whether it is %st(n) or FCTRL or FTAG or FSTATUS)
> there are insns
> e.g. 'ffree' changes FTAG register, so we must record it.
>
> Do you mean to say that we should remove it from just enumaration ?
> but anyway we need to record those registers.
>

You are working on make prec x86 support fp insn, not to extend the fp
function of i386 (If you want, you can make a special patch for it).




>
> --- On Wed, 7/1/09, Hui Zhu <teawater@gmail.com> wrote:
>
>> From: Hui Zhu <teawater@gmail.com>
>> Subject: Re: i386.record.floating.point.patch : with more testing and assurity
>> To: "paawan oza" <paawan1982@yahoo.com>, "Pedro Alves" <pedro@codesourcery.com>, "Mark Kettenis" <mark.kettenis@xs4all.nl>, "Michael Snyder" <msnyder@vmware.com>
>> Cc: gdb-patches@sourceware.org
>> Date: Wednesday, July 1, 2009, 11:23 AM
>> About this patch, I say my idea
>> again, I told in
>> http://sourceware.org/ml/gdb-patches/2009-06/msg00014.html
>> @@ -145,7 +145,22 @@
>>    I386_ES_REGNUM,
>>     /* %es */
>>    I386_FS_REGNUM,
>>     /* %fs */
>>    I386_GS_REGNUM,
>>     /* %gs */
>> -  I386_ST0_REGNUM
>>     /* %st(0) */
>> +  I386_ST0_REGNUM,
>>     /* %st(0) */
>> +  I386_ST1_REGNUM,
>>     /* %st(1) */
>> +  I386_ST2_REGNUM,
>>     /* %st(2) */
>> +  I386_ST3_REGNUM,
>>     /* %st(3) */
>> +  I386_ST4_REGNUM,
>>     /* %st(4) */
>> +  I386_ST5_REGNUM,
>>     /* %st(5) */
>> +  I386_ST6_REGNUM,
>>     /* %st(6) */
>> +  I386_ST7_REGNUM,
>>     /* %st(7) */
>> +  I386_FCTRL,
>>     /* floating point env regs : FCTRL-FOP
>> */
>> +  I386_FSTAT,
>> +  I386_FTAG,
>>
>> +  I386_FISEG,
>> +  I386_FIOFF,
>> +  I386_FOSEG,
>> +  I386_FOOFF,
>> +  I386_FOP
>>  };
>>
>> You are working on make prec x86 support fp insn, not to
>> extend the fp
>> function of i386 (If you want, you can make a special patch
>> for it).
>>
>> Hui
>>
>> On Tue, Jun 30, 2009 at 23:05, paawan oza<paawan1982@yahoo.com>
>> wrote:
>> >
>> > Hi,
>> > As I am submitting the patch for the first time, I am
>> not much aware of gdb test suite.
>> > would you please guide me about how I can put the
>> things in the testsuite ?
>> > is it the testsuite which comes along with the gdb
>> source ?
>> > gdb\testsuite\gdb.base ??
>> > Regards,
>> > Oza.
>> >
>> > --- On Tue, 6/30/09, Pedro Alves <pedro@codesourcery.com>
>> wrote:
>> >
>> >> From: Pedro Alves <pedro@codesourcery.com>
>> >> Subject: Re: i386.record.floating.point.patch :
>> with more testing and assurity
>> >> To: gdb-patches@sourceware.org
>> >> Cc: "paawan oza" <paawan1982@yahoo.com>,
>> teawater@gmail.com
>> >> Date: Tuesday, June 30, 2009, 7:09 PM
>> >> On Tuesday 30 June 2009 14:23:30,
>> >> paawan oza wrote:
>> >> >
>> >> > > As suggested by Hui,
>> >> > > I have come up with more detailed and
>> granular
>> >> test case
>> >> > > for the patch which I had submitted last
>> week.
>> >>
>> >> Could you please consider migrating that test into
>> the
>> >> testsuite?
>> >> You've gone through the trouble of writing tests
>> to make
>> >> sure
>> >> the features work now --- putting it in the
>> testsuite means
>> >> we
>> >> have an automatic-ish means to check that it
>> doesn't get
>> >> inadvertently broken in the future.  The way it
>> is,
>> >> when your
>> >> code gets in, the test will probably end up lost
>> in the
>> >> archives.
>> >> We wouldn't want that, would we?  :-)  Having
>> >> auto-tests, also helps
>> >> the person doing the review in confirming things
>> work as
>> >> expected (without much effort).
>> >>
>> >> --
>> >> Pedro Alves
>> >>
>> >
>> >
>> >
>> >
>>
>
>
>
>


  reply	other threads:[~2009-07-02  2:02 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01 15:59 paawan oza
2009-07-02  2:02 ` Hui Zhu [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-03 18:55 paawan oza
2009-07-03 21:52 ` Michael Snyder
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-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=daef60380907011901t30682c3fsaeb0d18be3aa0260@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=msnyder@vmware.com \
    --cc=paawan1982@yahoo.com \
    --cc=pedro@codesourcery.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