public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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: Thu, 28 Dec 2023 21:31:42 +0100	[thread overview]
Message-ID: <a955dc0c-1d58-4790-94ff-d69ff9173b3c@gmx.de> (raw)
Message-ID: <20231228203142.eJDf90mpdodtdo0RpmWCoh0R7sMJW_LTxctLPEJpmTM@z> (raw)
In-Reply-To: <CAFmAMQ28JZYXf7bpw1rHN=GUgtdWD9VYe+QQOJpa=_eB+r1s1g@mail.gmail.com>

Hi Rimvydas!

Am 28.12.23 um 08:09 schrieb Rimvydas Jasinskas:
> On Wed, Dec 27, 2023 at 10:34 PM Harald Anlauf <anlauf@gmx.de> wrote:
>> The patch is almost fine, except for a strange wording here:
>>
>> +@smallexample
>> +gfortran -save-temps -c foo.F90
>> +@end smallexample
>> +
>> +preprocesses to in @file{foo.fii}, compiles to an intermediate
>> +@file{foo.s}, and then assembles to the (implied) output file
>> +@file{foo.o}, whereas:
>>
>> I understand the formulation is copied from gcc/doc/invoke.texi,
>> where it does not fully make sense to me either.
>>
>> How about:
>>
>> "preprocesses input file @file{foo.F90} to @file{foo.fii}, ..."
>>
>> Furthermore,
>>
>> +@smallexample
>> +gfortran -save-temps -S foo.F
>> +@end smallexample
>> +
>> +saves the (no longer) temporary preprocessed file in @file{foo.fi}, and
>> +then compiles to the (implied) output file @file{foo.s}.
>>
>> Even if this is copied from the gcc texinfo file, how about:
>>
>> "saves the preprocessor output in @file{foo.fi}, ..."
>>
>> which I find easier to read.
>>
>> Can you also add a reference to the PR number in the commit message?
> I agree, wording sounds a lot better, included in v2 together with PR number.

Yes, this is OK.

Pushed: https://gcc.gnu.org/g:2cb93e6686e4af5725d8c919cf19f535a7f3aa33

Thanks for the patch!

>>> Is there a specific reason thy -fc-prototypes (Interoperability
>>> Options section) is excluded from manpage?
>>
>> Can you be more specific?  I get here (since gcc-9):
>>
>> % man /opt/gcc/14/share/man/man1/gfortran.1 |grep -A 1 "Interoperability
>> Options"
>>          Interoperability Options
>>              -fc-prototypes -fc-prototypes-external
>>
>> although no detailed explanation (-> gfortran.info).
> The https://gcc.gnu.org/onlinedocs/gfortran/Invoking-GNU-Fortran.html
> does contain a working link to
> https://gcc.gnu.org/onlinedocs/gfortran/Interoperability-Options.html
> However the manpage has Interoperability section explicitly disabled
> with "@c man end" ... "@c man begin ENVIRONMENT".
> After digging into git log it seems that Interoperability section was
> unintentionally added after this comment mark in
> https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=e655a6cc43

Yes, that might have been unintentional.

Can you open a PR, and if you have a fix, attach it there?

Thanks,
Harald

> Best regards,
> Rimvydas



  reply	other threads:[~2023-12-28 20:31 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
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 [this message]
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=a955dc0c-1d58-4790-94ff-d69ff9173b3c@gmx.de \
    --to=anlauf@gmx.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    /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).