From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30138 invoked by alias); 5 Jun 2009 02:41:15 -0000 Received: (qmail 30084 invoked by uid 22791); 5 Jun 2009 02:41:14 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from web36201.mail.mud.yahoo.com (HELO web36201.mail.mud.yahoo.com) (209.191.68.227) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Fri, 05 Jun 2009 02:41:07 +0000 Received: (qmail 45734 invoked by uid 60001); 5 Jun 2009 02:41:05 -0000 Message-ID: <422342.45652.qm@web36201.mail.mud.yahoo.com> Received: from [123.237.139.172] by web36201.mail.mud.yahoo.com via HTTP; Thu, 04 Jun 2009 19:41:05 PDT Date: Fri, 05 Jun 2009 02:41:00 -0000 From: paawan oza Subject: Re: Submition of i386.record.floating.point.patch To: Hui Zhu Cc: gdb-patches@sourceware.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-06/txt/msg00089.txt.bz2 Hi Hui, I think, FCTRL, FTAG, FOP are part of i386 also. for e.g. FFREE insn, changes only tag register. frstor affetcs whole FPU environment. The FPU operating environment consists of the FPU control word, status word, tag word, instruction pointer, data pointer, and last opcode. we need them for i386 too. I have sent the test_float.c in my previous mail, where you will find all these registers getting changed and tested. Regards, Oza. --- On Fri, 6/5/09, Hui Zhu wrote: > From: Hui Zhu > Subject: Re: Submition of i386.record.floating.point.patch > To: "paawan oza" > Cc: gdb-patches@sourceware.org > Date: Friday, June 5, 2009, 3:48 AM > >> diff -urN > gdb.orig/i386-tdep.h gdb.new/i386-tdep.h > >> --- gdb.orig/i386-tdep.h 2009-05-17 > 17:56:44.000000000 -0400 > >> +++ gdb.new/i386-tdep.h 2009-05-31 > 16:33:14.000000000 -0400 > >> @@ -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 > >> }; > >> > > > > About this part, I think this is my mistake. I > didn't take fp work > > for now very clear (Or I am still not clear with x86 > fp). > > FCTRL, FOP and so on are the fp reg of amd64. For > now, prec is still > > not support amd64 (I am working on it). > > 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. > > > > > > > > What do you think about my idea? >