From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Harald Anlauf <anlauf@gmx.de>
Cc: Tobias Burnus <tobias@codesourcery.com>,
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: Tue, 2 Jan 2024 11:37:03 -0800 [thread overview]
Message-ID: <ZZRl34pLvfHUwvvx@troutmask.apl.washington.edu> (raw)
In-Reply-To: <b652d029-3456-46b9-bff8-d0fd1e36667f@gmx.de>
On Tue, Jan 02, 2024 at 08:31:15PM +0100, Harald Anlauf wrote:
>
> we might want to update changes.html to reflect this. How about:
>
> diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
> index 403feb06..9b16f5e3 100644
> --- a/htdocs/gcc-14/changes.html
> +++ b/htdocs/gcc-14/changes.html
> @@ -284,6 +284,11 @@ a work-in-progress.</p>
>
> <h3 id="fortran">Fortran</h3>
> <ul>
> + <li>The compiler now accepts the <code>-std=f2023</code> option, which
> + has been added in preparation of support of Fortran 2023. This option
> + increases the line-length limit for source in free-form to 10000, and
> + statements may have up to 1 million characters.
> + </li>
> <li> With the <code>-save-temps</code> option, preprocessed files
> with the <code>.fii</code> extension will be generated from
> free-form source files such as <code>.F90</code> and
>
LGTM.
--
Steve
next prev parent reply other threads:[~2024-01-02 19:37 UTC|newest]
Thread overview: 9+ 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-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 ` [Patch] Fortran: Accept -std=f2023, update line-length for Fortran 2023 Mikael Morin
2023-11-17 19:07 ` Harald Anlauf
2024-01-02 19:31 ` Harald Anlauf
2024-01-02 19:37 ` Steve Kargl [this message]
2024-01-02 19:51 ` Harald Anlauf
2023-11-17 3:38 ` [Patch] Fortran: Accept -std=f2023 support, " Jerry D
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=ZZRl34pLvfHUwvvx@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--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).