Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 2/2] Wrap-up expression support for DFP.
Date: Wed, 02 Jan 2008 16:42:00 -0000	[thread overview]
Message-ID: <1199291677.12907.67.camel@localhost.localdomain> (raw)
In-Reply-To: <uejd5yb6c.fsf@gnu.org>

On Sat, 2007-12-29 at 13:47 +0200, Eli Zaretskii wrote:
> > From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> > Cc: gdb-patches@sourceware.org
> > Date: Fri, 28 Dec 2007 02:33:07 -0200
> > 
> > I couldn't find an appropriate place to put these in the manual, so I
> > went ahead and created a new sub-section, under "Examining Data". What
> > do you think?
> 
> I think a better place is in the "C and C++" section.  These are C/C++
> data types, aren't they?
> 
> > +There are two encodings in use, depending on the architecture: BID (Binary
> > +Integer Decimal) for x86 and x86-64, and DPD (Densely Packed Decimal) for
> > +PowerPC. GDB will use the appropriate encoding for the configured target.
> 
> PLease use "@value{GDBN}" instead of a literal "GDB".
> 
> > +Because of a limitation in libdecnumber, the library used by @value{GDBN}
> 
> "libdecnumber" is a file name, so it should have the @file markup.
> 
> > +point computations, error checking in decimal float operations ignore underflow,
> 
> "ignores".
> 
> Other than these comments, the patch is okay to go in (as a subsection
> of the "C and C++" section.

Ok, changed the patch to abide to all observations above. I will commit
it when the code patch is approved as well. Thanks for your review.
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center


      reply	other threads:[~2008-01-02 16:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20  5:55 [patch 0/2] Complete expression support for Decimal Floating Point Thiago Jung Bauermann
2007-12-20  5:55 ` [patch 1/2] Recognize DFP types in casts Thiago Jung Bauermann
2007-12-20 15:24   ` Daniel Jacobowitz
2007-12-20 16:48     ` Thiago Jung Bauermann
2007-12-20 16:54       ` Thiago Jung Bauermann
2007-12-20 16:57       ` Daniel Jacobowitz
2007-12-20 17:21         ` Thiago Jung Bauermann
2007-12-20  8:03 ` [patch 2/2] Wrap-up expression support for DFP Thiago Jung Bauermann
2007-12-21 16:12   ` Eli Zaretskii
2007-12-21 16:30     ` Andreas Schwab
2007-12-21 16:38       ` Eli Zaretskii
2007-12-27  7:40     ` Thiago Jung Bauermann
2007-12-29 11:21       ` Eli Zaretskii
2008-01-02 20:07         ` Thiago Jung Bauermann
2008-01-05 11:30           ` Eli Zaretskii
2008-01-07 16:20             ` Thiago Jung Bauermann
2008-01-07 17:09               ` Thiago Jung Bauermann
2008-01-07 21:09               ` Eli Zaretskii
2008-01-07 22:39                 ` Thiago Jung Bauermann
2007-12-28  6:16     ` Thiago Jung Bauermann
2007-12-29 12:53       ` Eli Zaretskii
2008-01-02 16:42         ` Thiago Jung Bauermann [this message]

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=1199291677.12907.67.camel@localhost.localdomain \
    --to=bauerman@br.ibm.com \
    --cc=eliz@gnu.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