public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Pierre-Marie de Rodat <pmderodat@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r11-6217] [Ada] Minor comment fix in System.Val_Real
Date: Thu, 17 Dec 2020 10:51:47 +0000 (GMT)	[thread overview]
Message-ID: <20201217105147.5071038708F9@sourceware.org> (raw)

https://gcc.gnu.org/g:e2ff35b910f0c9a59d1ae64c142fb5866126f09f

commit r11-6217-ge2ff35b910f0c9a59d1ae64c142fb5866126f09f
Author: Eric Botcazou <ebotcazou@adacore.com>
Date:   Sat Dec 5 08:53:16 2020 +0100

    [Ada] Minor comment fix in System.Val_Real
    
    gcc/ada/
    
            * libgnat/s-valrea.adb (Need_Extra): Fix comment.

Diff:
---
 gcc/ada/libgnat/s-valrea.adb | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/gcc/ada/libgnat/s-valrea.adb b/gcc/ada/libgnat/s-valrea.adb
index 9614760199d..0ac3846542b 100644
--- a/gcc/ada/libgnat/s-valrea.adb
+++ b/gcc/ada/libgnat/s-valrea.adb
@@ -43,10 +43,10 @@ package body System.Val_Real is
    --  We need an unsigned type large enough to represent the mantissa
 
    Need_Extra : constant Boolean := Num'Machine_Mantissa > Uns'Size - 4;
-   --  If the mantissa of the floating-point type is almost as large as that
-   --  of the unsigned type, we do not have enough space for an extra digit
-   --  in the unsigned type so we handle the extra digit separately, at the
-   --  cost of a potential roundoff error.
+   --  If the mantissa of the floating-point type is almost as large as the
+   --  unsigned type, we do not have enough space for an extra digit in the
+   --  unsigned type so we handle the extra digit separately, at the cost of
+   --  a potential roundoff error.
 
    Precision_Limit : constant Uns :=
      (if Need_Extra then 2**Num'Machine_Mantissa - 1 else 2**Uns'Size - 1);


                 reply	other threads:[~2020-12-17 10:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20201217105147.5071038708F9@sourceware.org \
    --to=pmderodat@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).