public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Paul Clarke <pc@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-8247] docs: Fix 'modff' reference in extend.texi
Date: Mon, 25 Apr 2022 14:49:32 +0000 (GMT)	[thread overview]
Message-ID: <20220425144932.3A2503857C46@sourceware.org> (raw)

https://gcc.gnu.org/g:235f88dbc3494c49e0f361a5a3f78491f72ff47c

commit r12-8247-g235f88dbc3494c49e0f361a5a3f78491f72ff47c
Author: Paul A. Clarke <pc@us.ibm.com>
Date:   Mon Apr 11 11:18:28 2022 -0500

    docs: Fix 'modff' reference in extend.texi
    
    In commit a2a919aa501e3 (2003), built-ins for modf and modff were added.
    In extend.texi, section "Other Builtins", "modf" was added to the paragraph
    "There are also built-in versions of the ISO C99 functions [...]" and
    "modf" was also added to the paragraph "The ISO C90 functions [...]".
    "modff" was not added to either paragraph.
    
    Based on the context clues about where "modfl" and other similar function
    pairs like "powf/powl" appear, I believe the reference to "modf" in the
    first paragraph (C99) should instead be "modff".
    
    2022-04-25  Paul A. Clarke  <pc@us.ibm.com>
    
    gcc
            * doc/extend.texi (Other Builtins): Correct reference to 'modff'.

Diff:
---
 gcc/doc/extend.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 931e5ae3769..84e6f6694ab 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -13460,7 +13460,7 @@ There are also built-in versions of the ISO C99 functions
 @code{expl}, @code{fabsf}, @code{fabsl}, @code{floorf}, @code{floorl},
 @code{fmodf}, @code{fmodl}, @code{frexpf}, @code{frexpl}, @code{ldexpf},
 @code{ldexpl}, @code{log10f}, @code{log10l}, @code{logf}, @code{logl},
-@code{modfl}, @code{modf}, @code{powf}, @code{powl}, @code{sinf},
+@code{modfl}, @code{modff}, @code{powf}, @code{powl}, @code{sinf},
 @code{sinhf}, @code{sinhl}, @code{sinl}, @code{sqrtf}, @code{sqrtl},
 @code{tanf}, @code{tanhf}, @code{tanhl} and @code{tanl}
 that are recognized in any mode since ISO C90 reserves these names for


                 reply	other threads:[~2022-04-25 14:49 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=20220425144932.3A2503857C46@sourceware.org \
    --to=pc@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).