public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: zheng <sch_zheng@163.com>, gcc@gcc.gnu.org
Subject: Re: Reporting a typo in gfortran intrinsic procedure webpage
Date: Wed, 3 Feb 2021 15:02:48 -0700	[thread overview]
Message-ID: <c54c782a-a101-e788-3048-81e457f232f0@redhat.com> (raw)
In-Reply-To: <135cc7b8.8ae.17737128446.Coremail.sch_zheng@163.com>

[-- Attachment #1: Type: text/plain, Size: 266 bytes --]



On 1/24/21 6:04 PM, zheng via Gcc wrote:
> I'd like to report a typo on page  https://gcc.gnu.org/onlinedocs/gfortran/ANINT.html#ANINT .  In the last table on this webpage, AINT should be ANINT.
Thanks.  This is what I pushed to the trunk to fix the typo:


Jeff

[-- Attachment #2: P --]
[-- Type: text/plain, Size: 907 bytes --]

commit 34215a7a3a359d700a520f1d5bdaec835f0b5180
Author: Jeff Law <law@redhat.com>
Date:   Wed Feb 3 15:01:19 2021 -0700

    Fix typo in Fortran manual
    
    gcc/fortran:
            * intrinsic.texi (ANINT): Fix typo.

diff --git a/gcc/fortran/intrinsic.texi b/gcc/fortran/intrinsic.texi
index 5debe94773b..63416bce7fd 100644
--- a/gcc/fortran/intrinsic.texi
+++ b/gcc/fortran/intrinsic.texi
@@ -1232,7 +1232,7 @@ end program test_anint
 @item @emph{Specific names}:
 @multitable @columnfractions .20 .20 .20 .25
 @item Name            @tab Argument         @tab Return type      @tab Standard
-@item @code{AINT(A)}  @tab @code{REAL(4) A} @tab @code{REAL(4)}   @tab Fortran 77 and later
+@item @code{ANINT(A)}  @tab @code{REAL(4) A} @tab @code{REAL(4)}   @tab Fortran 77 and later
 @item @code{DNINT(A)} @tab @code{REAL(8) A} @tab @code{REAL(8)}   @tab Fortran 77 and later
 @end multitable
 @end table

      reply	other threads:[~2021-02-03 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25  1:04 zheng
2021-02-03 22:02 ` Jeff Law [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=c54c782a-a101-e788-3048-81e457f232f0@redhat.com \
    --to=law@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=sch_zheng@163.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).