From: Harald Anlauf <anlauf@gmx.de>
To: Rimvydas Jasinskas <rimvydasjas@gmail.com>,
Rimvydas Jasinskas via Fortran <fortran@gcc.gnu.org>,
gcc-patches@gnu.org
Subject: Re: Fortran: Use non conflicting file extensions for intermediates [PR81615]
Date: Wed, 20 Dec 2023 20:29:49 +0100 [thread overview]
Message-ID: <c662cf49-f768-4682-9a9e-1d939ed0b3d4@gmx.de> (raw)
In-Reply-To: <CAFmAMQ214FmTReOkMaxCuxEiCKO7gWGAittA=H08K3x8ewTJbw@mail.gmail.com>
Am 20.12.23 um 05:32 schrieb Rimvydas Jasinskas:
> Dear all,
>
> In the spirit of c/c++ using the .i/.ii extensions for intermediates,
> use the .fi/.fii intermediate extensions for gfortran fixed/free form
> sources when -save-temps is invoked to avoid various issues.
I checked with Jerry on Mattermost that there are no objections
regarding the suffixes.
Pushed: https://gcc.gnu.org/g:ba615557a4c698d27042a5fe058ea6e721a03b12
Thanks for the patch!
> The documentation part will be submitted separately, because it
> involves adding a "Developer options" mini-section (as suggested by
> Harald) and moving the -fdump-* options from "Options for debugging
> your program or GNU Fortran" section.
Documentation improvements are always great!
> Regards,
> Rimvydas
Cheers,
Harald
WARNING: multiple messages have this Message-ID
From: Harald Anlauf <anlauf@gmx.de>
To: gcc-patches@gcc.gnu.org
Cc: fortran@gcc.gnu.org
Subject: Re: Fortran: Use non conflicting file extensions for intermediates [PR81615]
Date: Wed, 20 Dec 2023 20:29:49 +0100 [thread overview]
Message-ID: <c662cf49-f768-4682-9a9e-1d939ed0b3d4@gmx.de> (raw)
Message-ID: <20231220192949.WegAFbVNPLNxCyqr8_xkL7LFc_ajjxCGQzQCHSXA4Fk@z> (raw)
In-Reply-To: <CAFmAMQ214FmTReOkMaxCuxEiCKO7gWGAittA=H08K3x8ewTJbw@mail.gmail.com>
Am 20.12.23 um 05:32 schrieb Rimvydas Jasinskas:
> Dear all,
>
> In the spirit of c/c++ using the .i/.ii extensions for intermediates,
> use the .fi/.fii intermediate extensions for gfortran fixed/free form
> sources when -save-temps is invoked to avoid various issues.
I checked with Jerry on Mattermost that there are no objections
regarding the suffixes.
Pushed: https://gcc.gnu.org/g:ba615557a4c698d27042a5fe058ea6e721a03b12
Thanks for the patch!
> The documentation part will be submitted separately, because it
> involves adding a "Developer options" mini-section (as suggested by
> Harald) and moving the -fdump-* options from "Options for debugging
> your program or GNU Fortran" section.
Documentation improvements are always great!
> Regards,
> Rimvydas
Cheers,
Harald
next prev parent reply other threads:[~2023-12-20 19:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 4:32 Rimvydas Jasinskas
2023-12-20 19:29 ` Harald Anlauf [this message]
2023-12-20 19:29 ` Harald Anlauf
2023-12-24 1:33 ` Rimvydas Jasinskas
2023-12-27 20:34 ` Harald Anlauf
2023-12-27 20:34 ` Harald Anlauf
2023-12-28 7:09 ` Rimvydas Jasinskas
2023-12-28 20:31 ` Harald Anlauf
2023-12-28 20:31 ` Harald Anlauf
2023-12-30 11:01 ` Thomas Koenig
2023-12-30 11:08 ` Thomas Koenig
2024-01-01 21:25 ` Harald Anlauf
2024-01-01 21:25 ` 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=c662cf49-f768-4682-9a9e-1d939ed0b3d4@gmx.de \
--to=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).