From: Thomas Koenig <tkoenig@netcologne.de>
To: Rimvydas Jasinskas <rimvydasjas@gmail.com>,
Rimvydas Jasinskas via Fortran <fortran@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Fortran: Use non conflicting file extensions for intermediates [PR81615]
Date: Sat, 30 Dec 2023 12:08:41 +0100 [thread overview]
Message-ID: <f7db55b8-9150-4e54-b172-69e98ae57e03@netcologne.de> (raw)
In-Reply-To: <690db968-ef66-40ae-9626-d6631a7571dc@netcologne.de>
Replying to myself...
> I think this also desevers a mention in changes.html. Here is something
> that I came up with. OK? Or does anybody have suggestions for a better
> wording?
>
Or maybe this is better:
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 4b83037a..d232f631 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -282,8 +282,14 @@ a work-in-progress.</p>
<!-- <h3 id="d">D</h3> -->
-<!-- <h3 id="fortran">Fortran</h3> -->
-
+<h3 id="fortran">Fortran</h3>
+<ul>
+ <li> With the <code>-save-temps</code> option, preprocessed files
+ with the <code>.fii</code> extension will be generated for
+ free-form source files such as <code>.F90</code> and
+ <code>.fi</code> for fixed-form files such as <code>.F</code>.
+ </li>
+</ul>
<!-- <h3 id="go">Go</h3> -->
<!--
.................................................................. -->
next prev parent reply other threads:[~2023-12-30 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 4:32 Rimvydas Jasinskas
2023-12-20 19:29 ` Harald Anlauf
2023-12-24 1:33 ` Rimvydas Jasinskas
2023-12-27 20:34 ` Harald Anlauf
2023-12-28 7:09 ` Rimvydas Jasinskas
2023-12-28 20:31 ` Harald Anlauf
2023-12-30 11:01 ` Thomas Koenig
2023-12-30 11:08 ` Thomas Koenig [this message]
2024-01-01 21:25 ` Harald Anlauf
2024-01-02 8:16 ` Paul Richard Thomas
2024-01-02 9:01 ` Thomas Koenig
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=f7db55b8-9150-4e54-b172-69e98ae57e03@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=rimvydasjas@gmail.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).