public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "barrowes at alum dot mit.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/81615] save-temps and gfortran produces *.f90 files instead of *.i or *i90 files Date: Fri, 09 Dec 2022 13:25:24 +0000 [thread overview] Message-ID: <bug-81615-4-oKuUuZCu7c@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-81615-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81615 --- Comment #12 from Ben Barrowes <barrowes at alum dot mit.edu> --- I use these intermediate files during the software analysis process, but then delete them later. They are useful for me to have. When I am given a makefile, it is often 1000's loc. I am not sure I want to go in and modify it such as you suggest below and tell the customer it is for their own good. I'd rather be able to set a couple of switches to the preprocessor and get what I want. gfortran already allows to create a *.d file in each directory for each file. Is that poor software design as well? And when gfortran files are preprocessed all into a *.f90 file, except when they are not (see Thomas's email below), is that poor software design? ifort allows for the creation of these intermediate preprocessed files, creating *.i and *.i90 files. IBM XL allows this as well using the -d switch: https://www.ibm.com/docs/en/xl-fortran-aix/16.1.0?topic=preprocessor-passing-fortran-files-through-c And the intermediate filename becomes Ffilename.f* Can gfortran be modified to have the option to do this as well?
next prev parent reply other threads:[~2022-12-09 13:25 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-81615-4@http.gcc.gnu.org/bugzilla/> 2022-12-08 15:58 ` barrowes at alum dot mit.edu 2022-12-08 16:44 ` jakub at gcc dot gnu.org 2022-12-08 17:35 ` barrowes at alum dot mit.edu 2022-12-08 17:38 ` jakub at gcc dot gnu.org 2022-12-08 17:43 ` barrowes at alum dot mit.edu 2022-12-08 22:11 ` kargl at gcc dot gnu.org 2022-12-09 1:50 ` barrowes at alum dot mit.edu 2022-12-09 2:45 ` sgk at troutmask dot apl.washington.edu 2022-12-09 13:25 ` barrowes at alum dot mit.edu [this message] 2022-12-09 19:34 ` kargl at gcc dot gnu.org 2022-12-10 1:47 ` barrowes at alum dot mit.edu 2022-12-10 2:04 ` sgk at troutmask dot apl.washington.edu 2022-12-11 10:29 ` rimvydas.jas at gmail dot com 2023-12-19 13:29 ` acoplan at gcc dot gnu.org 2023-12-19 19:50 ` anlauf at gcc dot gnu.org 2023-12-19 20:04 ` jvdelisle at gcc dot gnu.org 2023-12-19 20:10 ` anlauf at gcc dot gnu.org 2023-12-20 19:24 ` cvs-commit at gcc dot gnu.org 2023-12-28 20:22 ` cvs-commit at gcc dot gnu.org 2023-12-29 20:26 ` anlauf at gcc dot gnu.org 2024-01-02 9:26 ` acoplan at gcc dot gnu.org
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=bug-81615-4-oKuUuZCu7c@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).