public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Steve Ellcey <sellcey@mips.com>, Carlos O'Donell <carlos@redhat.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
	<libc-ports@sourceware.org>,
	"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [PATCH] Speed up libm on MIPS
Date: Sat, 21 Sep 2013 18:47:00 -0000	[thread overview]
Message-ID: <alpine.DEB.1.10.1309211935060.4379@tp.orcam.me.uk> (raw)
In-Reply-To: <523C80A9.6070700@redhat.com>

On Fri, 20 Sep 2013, Carlos O'Donell wrote:

> > 2013-09-19  Steve Ellcey  <sellcey@mips.com>
> > 
> > 	* sysdeps/mips/fpu_control.h (_FPU_RC_MASK): New.
> > 	* sysdeps/mips/fpu/fegetround.c (fegetround): Use _FPU_RC_MASK.
> > 	* sysdeps/mips/fpu/fesetround.c (fesetround): Use _FPU_RC_MASK.
> 
> Looks good to me. You should just check this in as an obvious cleanup.

 Except with a small formatting fix to comply with the GNU Coding 
Standards:

On Fri, 20 Sep 2013, Steve Ellcey wrote:

> diff --git a/ports/sysdeps/mips/fpu_control.h b/ports/sysdeps/mips/fpu_control.h
> index 4046962..f26b736 100644
> --- a/ports/sysdeps/mips/fpu_control.h
> +++ b/ports/sysdeps/mips/fpu_control.h
> @@ -90,6 +90,8 @@ extern fpu_control_t __fpu_control;
>  #define _FPU_RC_ZERO    0x1
>  #define _FPU_RC_UP      0x2
>  #define _FPU_RC_DOWN    0x3
> +/* mask for rounding control */
> +#define _FPU_RC_MASK    0x3

-- the comment is expected to say:

/* Mask for rounding control.  */

i.e. start with a capital letter, end with a full stop and put two spaces 
exactly after the full stop.

 According to the GNU Coding Standards all comments have to be proper 
sentences with two spaces following every punctuation mark ending a 
sentence.  For further details please refer to:

http://www.gnu.org/prep/standards/standards.html#Comments

  Maciej

  reply	other threads:[~2013-09-21 18:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19 22:58 Steve Ellcey
2013-09-20  3:32 ` Carlos O'Donell
2013-09-20 16:51   ` Steve Ellcey
2013-09-20 17:06     ` Carlos O'Donell
2013-09-21 18:47       ` Maciej W. Rozycki [this message]
2013-09-22 17:40         ` Carlos O'Donell
2013-09-23 16:42           ` Steve Ellcey
2013-09-20 15:01 ` Richard Henderson
2013-09-20 15:35 ` Joseph S. Myers

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=alpine.DEB.1.10.1309211935060.4379@tp.orcam.me.uk \
    --to=macro@codesourcery.com \
    --cc=carlos@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-ports@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=sellcey@mips.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).