From: Wu Zhou <woodzltc@cn.ibm.com>
To: drow@false.org
Cc: gdb-patches@sourceware.org
Subject: About decimal floating point support
Date: Tue, 13 Jun 2006 15:51:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0606132327010.6826@localhost.localdomain> (raw)
Hi Daniel,
We ever talked about adding decimal floating point into GDB. And you
provided a lot insightful suggestion for my first patch. In my post at
2005-10-18:
http://sources.redhat.com/ml/gdb-patches/2005-10/msg00148.html
http://sources.redhat.com/ml/gdb-patches/2005-10/msg00149.html
I revised the patch and the testcase. I believe it can address most of
your concern.
But there is one concern not addressed: you ever proposed to move
libdecnumber to the top level of the repository, and use that to implement
DFP support in GDB. At that time (Oct, 2005), DFP support for gcc is not
matured yet. The libdecnumber code may change itself. So I didn't bother
to adopt you method at that time and put my focus on resolving other
problem you pointed out. Now since DFP is already in the 4.2 development
tree of gcc. So I guess it is time to revist this.
What is your current thought about this? Do you still think it is more
feasible to put libdecnumber at the top level repository? I am now
considering copy the code of libdecnumber (which is at the top level of
gcc repository) to the top level of gdb repository. and use that to
re-implment DFP support. If the code of libdecnumber is changed, we can
synchronize that to gdb repository. Then gdb developers don't need to
maintain these sensitive numeric code.
What do you think on this? Your comments are highly appreciated!
Regards
- Wu Zhou
next reply other threads:[~2006-06-13 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 15:51 Wu Zhou [this message]
2006-06-13 17:40 ` Daniel Jacobowitz
2006-06-13 19:02 ` DJ Delorie
2006-06-13 19:17 ` Daniel Jacobowitz
2006-06-14 1:10 ` Wu Zhou
2006-06-14 2:47 ` Daniel Jacobowitz
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=Pine.LNX.4.64.0606132327010.6826@localhost.localdomain \
--to=woodzltc@cn.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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