From: Mikael Morin <morin-mikael@orange.fr>
To: Tobias Burnus <tobias@codesourcery.com>,
Harald Anlauf <anlauf@gmx.de>,
gcc-patches <gcc-patches@gcc.gnu.org>,
fortran <fortran@gcc.gnu.org>
Subject: Re: [Patch] Fortran: Accept -std=f2023, update line-length for Fortran 2023
Date: Fri, 17 Nov 2023 13:06:59 +0100 [thread overview]
Message-ID: <78bd4211-936c-4c3f-b57e-c08fc49345f6@orange.fr> (raw)
In-Reply-To: <6b62f178-e3c4-4bdb-b7cc-eb57477cd27d@codesourcery.com>
Le 17/11/2023 à 12:38, Tobias Burnus a écrit :
>
> Unless there are follow up comments, I will commit it later today.
>
I skimmed quickly through the patch, and noticed one typo to fix:
> diff --git a/gcc/fortran/invoke.texi b/gcc/fortran/invoke.texi
> index 10387e39501..5f87b330a22 100644
> --- a/gcc/fortran/invoke.texi
> +++ b/gcc/fortran/invoke.texi
> @@ -958,8 +959,8 @@ The following example will trigger the warning.
> @item -Wampersand
> Warn about missing ampersand in continued character constants. The
> warning is given with @option{-Wampersand}, @option{-pedantic},
> -@option{-std=f95}, @option{-std=f2003}, @option{-std=f2008} and
> -@option{-std=f2018}. Note: With no ampersand given in a continued
> +@option{-std=f95}, @option{-std=f2003}, @option{-std=f2008},
@option{-std=f2018}
> +and @option{-std=f203}. Note: With no ampersand given in a continued
> character constant, GNU Fortran assumes continuation at the first
> non-comment, non-whitespace character after the ampersand that
> initiated the continuation.
s/f203/f2023/
next prev parent reply other threads:[~2023-11-17 12:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 13:01 [Patch] Fortran: Accept -std=f2023 support, " Tobias Burnus
2023-11-16 19:30 ` Harald Anlauf
2023-11-16 19:30 ` Harald Anlauf
2023-11-17 11:38 ` [Patch] Fortran: Accept -std=f2023, update line-length for Fortran 2023 (was: [Patch] Fortran: Accept -std=f2023 support, update line-length for Fortran 2023) Tobias Burnus
2023-11-17 12:06 ` Mikael Morin [this message]
2023-11-17 19:07 ` [Patch] Fortran: Accept -std=f2023, update line-length for Fortran 2023 Harald Anlauf
2023-11-17 19:07 ` Harald Anlauf
2024-01-02 19:31 ` Harald Anlauf
2024-01-02 19:31 ` Harald Anlauf
2024-01-02 19:37 ` Steve Kargl
2024-01-02 19:51 ` Harald Anlauf
2024-01-02 19:51 ` Harald Anlauf
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=78bd4211-936c-4c3f-b57e-c08fc49345f6@orange.fr \
--to=morin-mikael@orange.fr \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tobias@codesourcery.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).