From: paawan oza <paawan1982@yahoo.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Submition of i386.record.floating.point.patch
Date: Fri, 05 Jun 2009 02:41:00 -0000 [thread overview]
Message-ID: <422342.45652.qm@web36201.mail.mud.yahoo.com> (raw)
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 <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: 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?
>
next reply other threads:[~2009-06-05 2:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 2:41 paawan oza [this message]
2009-06-05 2:50 ` Hui Zhu
2009-06-05 2:56 ` Mark Kettenis
2009-06-05 2:58 ` Hui Zhu
-- 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 15:00 paawan oza
2009-06-12 5:19 ` Hui Zhu
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-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=422342.45652.qm@web36201.mail.mud.yahoo.com \
--to=paawan1982@yahoo.com \
--cc=gdb-patches@sourceware.org \
--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