From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 4E75C382FCAA; Fri,  9 Dec 2022 02:45:38 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4E75C382FCAA
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1670553938;
	bh=JW3lj7GrsNIZaXaykZELLY1mY3FmHUUdxRJVZtc6w4E=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=vGduUcnHUT5AkpIdkx0SPuCBO4t9qxXyjqHG4jGgez4ey/nkBl9wRMX+/QykCqtdO
	 2w987dIKRyUjUmuBgr7HynIoV4YNCVo0kEA/Mrx2iaiZcpwpdOfLrPGn0+gazBzQf8
	 0u/DkSp8BVRvaapQZKtLOazSLDQBzBx6682tcLO8=
From: "sgk at troutmask dot apl.washington.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 02:45:37 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-81615-4-U12OpVv7nL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81615-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81615-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81615

--- Comment #11 from Steve Kargl <sgk at troutmask dot apl.washington.edu> =
---
On Fri, Dec 09, 2022 at 01:50:56AM +0000, barrowes at alum dot mit.edu wrot=
e:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81615
>=20
> --- Comment #10 from Ben Barrowes <barrowes at alum dot mit.edu> ---
> The reason the stdout redirection doesn't work for me is because
> I want to save these preprocessed files during a "make" session.
> When I make, thousands of fotran files are preprocessed and compiled.
> How do I save the stdout from each one into its own directory?
>=20

% cat > a1.f90
subroutine foo
end subroutine foo
% cp a1.f90 b1.f90
% cp a1.f90 c1.f90
% cp a1.f90 d1.f90
% cat Makefile
FC =3D gfortran11
FF =3D -cpp -E
IN =3D f90
OUT =3D txt

NAMES =3D a1 b1 c1 d1

all:
.for i in ${NAMES}
        ${FC} ${FF} $i.${IN} > $i.${OUT}
.endfor
% make=20
gfortran11 -cpp -E a1.f90 > a1.txt
gfortran11 -cpp -E b1.f90 > b1.txt
gfortran11 -cpp -E c1.f90 > c1.txt
gfortran11 -cpp -E d1.f90 > d1.txt
% ls
Makefile        a1.txt          b1.txt          c1.txt          d1.txt
a1.f90          b1.f90          c1.f90          d1.f90

The preprocessed files appear in the same directory with its source
source file.  It's trivial matter to have preprocess stuffed into
its own directory.

PS: Having to preprocess thousands of Fortran files into individual
directories seems to be poor software design.=