Re: Fortran: Use non conflicting file extensions for intermediates [PR81615]

2023-12-27 Thread Rimvydas Jasinskas
inedocs/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 mar

Re: Fortran: Use non conflicting file extensions for intermediates [PR81615]

2023-12-23 Thread Rimvydas Jasinskas
From: Rimvydas Jasinskas Date: Sat, 23 Dec 2023 18:59:09 + Subject: Fortran: Add Developer Options mini-section to documentation Separate out -fdump-* options to the new section. Sort by option name. While there, document -save-temps intermediates. gcc/fortran/ChangeLog: * invoke.texi: Add

Fortran: Use non conflicting file extensions for intermediates [PR81615]

2023-12-19 Thread Rimvydas Jasinskas
"Developer options" mini-section (as suggested by Harald) and moving the -fdump-* options from "Options for debugging your program or GNU Fortran" section. Regards, Rimvydas From d313ccb110c5418260b667c5f289a249247de059 Mon Sep 17 00:00:00 2001 From: Rimvydas Jasinskas Date: Wed,

Re: Support for WEAK attribute, part 2

2023-02-23 Thread Rimvydas Jasinskas via Gcc-patches
e addressed in the future. > Finally, please do not forget to CC patches to gcc-patches@ > so that others can see them. Out of curiosity, what is the purpose of CC patches to gcc-patches too? Attachments are even available in web mailing list too, like in: https://gcc.gnu.org/pipermail/for