From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/i387] improve the output of 'info float' (was: "Re: gdb-patch mailing list")
Date: Sun, 03 Jan 2010 10:46:00 -0000 [thread overview]
Message-ID: <E1NRNyP-00083A-09@fencepost.gnu.org> (raw)
In-Reply-To: <20100103053213.GA2788@adacore.com> (message from Joel Brobecker on Sun, 3 Jan 2010 09:32:13 +0400)
> Date: Sun, 3 Jan 2010 09:32:13 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> > + /* Precision */
> > + fprintf_filtered (file, "%s ", (status & 0x0020) ? "PE" : " ");
> > + /* Underflow */
> > + fprintf_filtered (file, "%s ", (status & 0x0010) ? "UE" : " ");
> > + /* Overflow */
> > + fprintf_filtered (file, "%s ", (status & 0x0008) ? "OE" : " ");
> > + /* Zero Devide */
> > + fprintf_filtered (file, "%s ", (status & 0x0004) ? "ZE" : " ");
> > + /* Denormalized operand */
> > + fprintf_filtered (file, "%s ", (status & 0x0002) ? "DE" : " ");
> > + /* Invalid operation */
> > + fprintf_filtered (file, "%s ", (status & 0x0001) ? "IE" : " ");
>
> I personally think that the added comments are overkill, but I'm
> otherwise OK with them. Mark might have a different opinion on this.
I'm not Mark, but how exactly are these comments overkill? Unless
someone knows by heart the bits in the x87 FP Status word, or can
decipher the two-letter abbreviations without consulting the Intel
manuals, I'd say they add significantly to the readability of the
source code.
However, these comments need to be formatted according to coding
standards, as in
/* Denormalized operand. */
(i.e. ended with a period and 2 spaces), and also proofread for typos,
like this one:
> > + /* Zero Devide */
prev parent reply other threads:[~2010-01-03 10:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B3E4DC6.7020901@cyberfiber.org>
[not found] ` <20100102043704.GR548@adacore.com>
2010-01-02 8:29 ` gdb-patch mailing list Michael
2010-01-02 8:48 ` Michael
[not found] ` <20100102093213.GX2788@adacore.com>
2010-01-02 9:33 ` Joel Brobecker
[not found] ` <4B3F252A.30504@cyberfiber.org>
[not found] ` <20100102111708.GV548@adacore.com>
2010-01-02 11:56 ` Michael
2010-01-03 5:32 ` [RFA/i387] improve the output of 'info float' (was: "Re: gdb-patch mailing list") Joel Brobecker
2010-01-03 8:46 ` Mark Kettenis
2010-01-03 10:47 ` [RFA/i387] improve the output of 'info float' Michael
2010-01-03 10:52 ` Michael
2010-01-04 18:47 ` Michael
2010-01-03 10:46 ` Eli Zaretskii [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=E1NRNyP-00083A-09@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--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